On 05.06.2009, at 02:48, Howard Lewis Ship wrote:
> Again, I'm not sure what the solution is or what the implementation
> would look like, but I'd love it if Clojure could relate back to me,
> when an exception occurred, what lazy operations were taking place
> that caused the bad code to be invo
> 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 se
So the times when I have the most trouble in Clojure is related to
laziness. Using a lot of lazy operations (for, map, etc.) can cause
some grief. I was refactoring and added a new parameter to a somewhat
common function and didn't catch all the invocations. However, my
exception turned up in an
