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

> It's the reason why one of the biggest users of Haskell (and the most notable example of Haskell in industry), Standard Chartered, uses their own Haskell compiler that's strict by default.

No it's not. The reason Mu is strict is that it was designed to target an existing strict runtime.



That begs the question: why target Haskell to an existing strict runtime instead of using Haskell's own delayed evaluation runtime?


I always understood it to be for interoperability with existing software targeting that runtime, but I'm not sure that was more than assumption.


That is correct.




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

Search: