Conception, Evolution, and Application of Functional Programming Languages.

Hudak, P. (1989). Conception, Evolution, and Application of Functional Programming Languages. ACM Computing Surveys, 21(3), 359-411.

Type

Journal article

Intellectual base

Primary research

Year

1989

Volume

21

Issue

3

Pages

359-411

DOI

10.1145/72551.72554

DOI registrant

Association for Computing Machinery

Link

https://doi.org/10.1145/72551.72554

Cited from

philosophy

Cited by

3 citations across 3 artifacts.

Each citation links to the sentence it supports in the citing article.

Primes

• Latent Realizable Capacity
  • The persistence regime is precisely specifiable and is where languages differ: call-by-need depletes the capacity on first manifestation (the thunk is overwritten by its value, so the disposition is exercised once and replaced), whereas call-by-name preserves it

    This sourceDescribes lazy evaluation, thunks, and the call-by-need versus call-by-name distinction in which a thunk's capacity to compute is depleted-on-first-use versus preserved across forcings.

Domain-specific

• Applicative programming language
  • The entry treats a programming-language classification whose usage is partly historical; claims about a specific language must state version and core, and purity or safety properties require separate evidence.
• Graph reduction
  • The graph represents applications and values with shared nodes, non-strict evaluation selects a reducible expression only when demanded and updates the node with its result for all references.

Verification

Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.

Does it back the claim? Not recorded. Neither this nor any other of the 3 citations of this work carries a recorded support check.

Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Registry ID ref:80f0f12e2e6e · see in the full table