Pith. Sign in

RECORD

Functional or imperative? On pleasant semantics for differentiable programming languages

PaperPDF from arXiv

data files

Paper breakdownThe authors' claims, conditions and measurements, as JSON Signed receiptProof this review has not been altered
X Bluesky LinkedIn Reddit Hacker News
Michael Innes

Programming Languages · Submitted 22 Jun 2022

abstract compiled · 2026-09-23 · no language-model review

The authors' main claim This article explores why imperative and functional styles are used, and how future language designs might get the best of both worlds.

how it is stated · speculative 0.76 read the record →

Comment (0) Read on arXiv ↗
Cite ▾
arXiv ID2206.11192 (version 1)
Pith IDWEPLBBOJ, Pith's permanent record of this paper and its review
CitationMichael Innes. "Functional or imperative? On pleasant semantics for differentiable programming languages." arXiv:2206.11192 (2022). https://pith.science/paper/WEPLBBOJ
Claim paper

The compiled record

The paper's own sentences, arranged. Each label is drawn from a closed vocabulary; the number beside it is the probability the classifier gave that label. Numbers in the tables are the authors', checked by code. No sentence in this record was written by a model.

Open the compiled record

Compiled by classifier-1.13.0 via TypeSafe API, question bank abstract-p1-20260923, 2026-09-23: 1 request, 4,133 input tokens.

What the abstract itself states, as probabilities: claims first 0.03 · states limitation 0.06 · human participants 0.06 · controlled comparison 0.02 · randomized assignment 0.01 · states quantitative result 0.03 · compares with prior results 0.05 · mentions code or data availability 0.02.

The abstract, sentence by sentence

arXiv listing abstract v1. Results and the main claim are underlined; .

In machine learning (ML), researchers and engineers seem to be at odds. System implementers would prefer models to be declarative, with detailed type information and semantic restrictions that allow models to be optimised, rearranged and parallelised. Yet practitioners show an overwhelming preference for dynamic, imperative languages with mutable state, and much engineering effort is spent bridging the resulting semantic divide. Is there a fundamental conflict? This article explores why imperative and functional styles are used, and how future language designs might get the best of both worlds.

background contribution method result interpretation main claim

What the classifier reports for each sentence. The number is the probability it gave the label.
#sentencerolethe authors' own workstates the main conclusionstrength
s0 In machine learning (ML), researchers and engineers seem to be at odds. background 1.00 0.08 0.02 asserted 0.81
s1 System implementers would prefer models to be declarative, with detailed type information and semantic restrictions that allow models to be optimised, rearranged and parallelised. background 1.00 0.05 0.04 asserted 0.96
s2 Yet practitioners show an overwhelming preference for dynamic, imperative languages with mutable state, and much engineering effort is spent bridging the resulting semantic divide. background 0.98 0.09 0.05 asserted 1.00
s3 Is there a fundamental conflict? gap 0.70 0.03 0.02 unclear 0.96
s4 This article explores why imperative and functional styles are used, and how future language designs might get the best of both worlds. contribution 0.98 0.45 0.17 speculative 0.76

What kind of paper the classifier reports this is: position or commentary 1.00 · evidence from argument 0.99.

What was examined, and what was not

sources read
  • arXiv listing abstract v1
not examined
  • full text
  • figures and tables
  • references and citing sentences
  • relations to other papers
levels run
  • P abstract
not run
  • S sections
  • T body sentences
  • C citations
  • R cross-paper relations

Every quoted sentence on this record is the authors'. Every label is from Pith's closed vocabulary, with the probability shown beside it. Every number in the measurements table is the authors', checked by code. Record as JSON

The paper
Original abstract

In machine learning (ML), researchers and engineers seem to be at odds. System implementers would prefer models to be declarative, with detailed type information and semantic restrictions that allow models to be optimised, rearranged and parallelised. Yet practitioners show an overwhelming preference for dynamic, imperative languages with mutable state, and much engineering effort is spent bridging the resulting semantic divide. Is there a fundamental conflict? This article explores why imperative and functional styles are used, and how future language designs might get the best of both worlds.

Human review

How Pith checks papers → · Full audit of this paper →

How the literature uses it

What this paper does with the arXiv papers it cites

Each citing sentence is taken from the citing paper's LaTeX source and typed by Pith's classifier. A label appears at probability 0.8 or more (0.95 for support), a contest at 0.7 or more; the quoted words are the citing authors'. How each label was checked · JSON

Discussion

Know something about this paper? Leave a comment, or highlight any passage above to comment on it.