> I felt the same way at first. I think it would help if the group > shared some common, non-mathematical cases, where laziness is helpful.
I've been using multiple resultset-seq to collect together matching data from different databases and stream it on through some existing Java code. It is fast, and memory efficient. I don't have to even think about releasing memory or moving resultset cursors along. My algorithm can look ahead in the cached sequences without losing rows, and thanks to the common seq abstraction I can change the head of the pipeline to pump unit-test data through without changing the rest of the code. It is awesome. -- Dave --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
