Skip to main content

the second reason for laziness #

In Why Functional Programming Matters John Highes argues that a desire for modularity - the atomisation of a problem domain - leads structural programming to need new types of glue to stick components together.

graph LR; A[Modularity]-->B[composition]; B-->C[Profit]

laziness gives us transparent streaming

*** sum-type continuations are an anti-pattern

Faster Coroutine Pipelines: A Reconstruction

https://www.reddit.com/r/haskell/comments/11z8ueh/an_apologia_for_lazy_evaluation/

There's no articles to list here yet.