On Mon, Sep 3, 2012 at 1:58 PM, Stephen Compall <stephen.comp...@gmail.com> wrote: > On Sun, 2012-09-02 at 23:02 -0700, Ben Wolfson wrote: >> Can you say what this means (the note about take-while being called in >> coll order)? >> >> Does it mean that it's not a guarantee of the API that the predicate >> passed to take-while be called *successively* on the items in the >> collection passed in? > > Yes, that's what it means. Sorry I was not more clear.
Stephen, could you elaborate on this? My reading of the side-effect-free restriction was just that the predicate may be called on more elements than end up in the result, perhaps due to chunking or whatever. I'm not sure I see where there's any indication that take-while might call the predicate in a non-linear order - or is just one of those 'guilty by omission' situations? -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- 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
