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

If your language doesn't give you laziness, you're reinventing it yourself with strict primitives each time.


On the other hand, when you don't want laziness you really won't like if it's present anyways.


Lazy to strict is reasonably easy to do though. The problem is normally that once one bit goes strict, most other things implicitly do too.

Strict to lazy is normally a rewrite.


Lazy to strict is reasonably easy to do though. The problem is normally that once one bit goes strict, most other things implicitly do too.

Strict to lazy is normally a rewrite.


I think the scope of lazy constructs should usually be far less than that of strict constructs, so it's only in the cases where the librarified lazy abstractions don't fit that you need a rewrite. Lazy to strict isn't hard, but I don't want the performance and cognitive overhead of lazy-by-default.




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

Search: