A few days ago, Stuart Halloway and I had an offline discussion about some of the "gotchas" related to Clojure's laziness. He encouraged me to blog about my thoughts on the matter.
On a related note, about a month ago, I posted comments about Clojure's laziness. Rich's response was: "The argument you've made, however, is theoretical. I've tried what you said. In fact, it's sitting there in the implementation right now - just uncomment lazy-seq. cached-seq is there, as is a non-caching LazySeq class implementing ISeq, and all of the library functions can be defined in terms of it. I also did that, and then tried it and some common code. You should too, and report back your actual experience." So my blog post has a dual purpose. First, I explain the "gotcha" that Stuart and I discussed. Second, I report back to the community about the actual experience I had in the past month, exploring laziness in Clojure. I decided to blog it rather than post it here primarily due to its length. If you're at all interested in laziness, check it out: http://programming-puzzler.blogspot.com/ --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
