On Mon, Mar 3, 2014 at 3:06 AM, Mikera <mike.r.anderson...@gmail.com> wrote:
> ISeq itself isn't too bad (it's just an interface, as above), but some of > the implementations are a bit expensive. > ISeq is inherently not suited for performance critical code, as next() requires creation of a new object. Even if JVM handles such ephermal instances quite well, it still cannot compete with simple iterations or mutable iterators. -- 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 --- 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 clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
