Lazy versus strict

Research output: Contribution to journalArticlepeer-review

Abstract

Lazy or call-by-need languages schedule work dynamically by building closures and shunning side effects; strict or call-by-value languages avoid the overhead of closures and may exploit side effects. Each style has complementary advantages and complementary adherents. The gap between the lazy and strict camps has two dimensions, which we shall name style and models. Recent developments suggest that along both dimensions the gap is shrinking. We list some commercial applications of each kind of language and examine each dimension of difference in turn.
Original languageEnglish
Pages (from-to)318-320
Number of pages3
JournalACM Computing Surveys
Volume28
Issue number2
DOIs
Publication statusPublished - 1 Jun 1996

Fingerprint Dive into the research topics of 'Lazy versus strict'. Together they form a unique fingerprint.

Cite this