this post was submitted on 18 Aug 2023
5 points (100.0% liked)

Haskell

5 readers
1 users here now

**The Haskell programming language community.** Daily news and info about all things Haskell related: practical stuff, theory, types, libraries, jobs, patches, releases, events and conferences and more... ### Links - Get Started with Haskell

founded 2 years ago
 

Answering the question raised at the end of Part 1, we take a look at how a hypothetical Strict Haskell would tie the compilers hands despite pervasive purity. We also examine how laziness permits optimizations that come with no intrinsic cost and compare its benefits to a strict language with opt-in laziness.

you are viewing a single comment's thread
view the rest of the comments
[–] mangoiv@functional.cafe 1 points 2 years ago

@jaror second one was even more awesome than the first one! This view is something that makes it really possible to argue for laziness by default! Thank you @lexi_lambda!