Not necessarily, when combined with functions that take a variable number of arguments. Example:
user=> (do (apply concat () (range)) nil) nil If apply did realize the range lazy sequence, that form would never terminate rather than returning nil. In your case however memory failed me and I was mistaken: it actually *does* realize the sequence because `list` eagerly iterates over the argument list rather than constructing it lazily. Ignore my point about the overhead of creating the *-list lazy sequences, everything else still stands > On 12 May 2016, at 22:40, JvJ <[email protected]> wrote: > > I was under the impression that the call to "apply list" would realize the > lazy sequences beforehand. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
