Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Having used Mu I concluded that Haskell got function laziness correct. (Data type laziness is a different issue, but that can be solved by `StrictData`).


The problem with StrictData is that you need to convince every library in your dependency graph to switch to it, or provide strict versions of the data structures. Common container types like Map and Set do this. Your typical library implementing a domain-specific functionality does not.


Yup, that's right. Libraries can expose the wrong thing, or just space leak internally. Here's an example:

https://github.com/mrkkrp/megaparsec/issues/486




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: