yup. and i mean "i wish lisp had that ability, rather than forcing
everything that isn't strict-evaluation functional argument passing
into compile time macros."
of course, it only moves the newbie (like me with macros) "hey, these
things aren't all exactly the same?!" reaction somewhere else -- away
from macros, and on to "why does if(a,b) have different side-effect
results than foo(a,b)?!"
Pervasive laziness can be a curse itself; lots of Haskell programmers
expend effort to avoid it for performance reasons. Generally, things
are the way they are for a reason. (Not always true, but it's worth
finding out.)
Be careful what you wish for!
With the ease of manual thunking and delay, and Clojure's lazy
sequences -- the main place you want laziness -- I don't long for the
abandonment of eager evaluation.
--
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
