First-order laziness

Anton Lorenzen*, Daan Leijen, Wouter Swierstra, Sam Lindley

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

Abstract

In strict languages, laziness is typically modelled with explicit thunks that defer a computation until needed and memoize the result. Such thunks are implemented using a closure. Implementing lazy data structures using thunks thus has several disadvantages: closures cannot be printed or inspected during debugging; allocating closures requires additional memory, sometimes leading to poor performance; reasoning about the performance of such lazy data structures is notoriously subtle. These complications prevent wider adoption of lazy data structures, even in settings where they should shine. In this paper, we introduce lazy constructors as a simple first-order alternative to lazy thunks. Lazy constructors enable the thunks of a lazy data structure to be defunctionalized, yielding implementations of lazy data structures that are not only significantly faster but can easily be inspected for debugging.
Original languageEnglish
Article number261
Pages (from-to)734-762
Number of pages29
JournalProceedings of the ACM on Programming Languages
Volume9
Issue numberICFP
DOIs
Publication statusPublished - 5 Aug 2025

Keywords / Materials (for Non-textual outputs)

  • Laziness
  • Defunctionalization
  • Perceus

Fingerprint

Dive into the research topics of 'First-order laziness'. Together they form a unique fingerprint.

Cite this