Hi Brian, Laziness (and first class functions) can help with code modularity, I would suggest reading paper by John Hughes on the topic: www.cs.kent.ac.uk/people/staff/dat/miranda/whyfp90.pdf
Kurman On Tue, Oct 23, 2012 at 11:38 AM, Brian Craft <craft.br...@gmail.com> wrote: > I don't yet understand how laziness helps. Can anyone point me to a > reference? I have vague memory that one of the videos addresses this (I > remember something about "these are not iterators"), but I'm having trouble > finding it now. > > I'm finding that lazy seqs are too slow for everything, so I expect I'm > using them incorrectly. Many of the core functions return seqs, and I > invariably end up wrapping them with (vec ...) to get any kind of > reasonable performance. Is that what I should be doing? > > Is a lazy seq mostly about algorithmic clarity, and avoiding unnecessary > computation? So far I haven't run into any cases where I wouldn't realize > the entire sequence, and it's always faster to do it up-front. > > -- > 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 -- 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
