> I'm not sure what can be done about this kind of problem. The laziness > is wonderful until it breaks ... here's an area where Haskell would > have been able to identify the incorrect call via static analysis.
i guess that even in Haskell there are issues with laziness, at least in the wider sense of it there. i sure would like it if there were a paper that investigated and clearly defined the issues around various forms of laziness, and suggested how best to deal with them, to reduce the chance of suck. sincerely. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
