In my case I was just trying to ensure a list type for a java API, though perhaps the clojure reflection layer would have converted a non list seq to a list to match the call, I don't know.
On Mon, May 5, 2014 at 9:01 PM, Sean Corfield <s...@corfield.org> wrote: > My question would be: why do you specifically need a list? i.e., why isn't > a sequence good enough? > > Sean > > On May 3, 2014, at 6:30 AM, Dave Tenny <dave.te...@gmail.com> wrote: > > After nosing around all I've come up with via clojure mechanisms is to > use (apply list (sort ...)). > > It seems to work well enough for lists of arbitrary size (subject to > usual memory/size limitations of large lists). > > > > I also considered some native java abuse such as > java.util.Arrays.asList(Enumeration), > > though I didn't quickly find a way to convert the clojure.lang.ArraySeq > from my sort() in testing to an Enumeration. > > > > Guess I'm set for now, I was just hoping to avoid consing a new list on > my sort result in order to get a specific collection type. > > > -- 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/d/optout.
