This is great advice, of course. On the other hand, I feel it's important to be explicitly clear about which forms will hold on to (seemingly) transient data. Certain things are explicitly clear about this (such as the docstring for doseq), and this particular case is unfortunate because in the common case, loop doesn't hold on to the reference. I think the inconsistency in this case is dangerous, especially since loop/recur is the generic iteration construct.
On Nov 2, 12:59 pm, John Harrop <jharrop...@gmail.com> wrote: > In the meantime, remember that it's always worth trying to implement > seq-processing in terms of map, reduce, filter, for, and friends if > possible, or lazy-seq, before resorting to loop/recur. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
