On Fri, Mar 4, 2011 at 12:34 PM, Stuart Halloway <stuart.hallo...@gmail.com> wrote: > This is hardly unfortunate! The API is carefully designed: object args come > > first, seq args come last. > > Eh, not always: conj, nth, and several others put seq args first, > though cons can be used on seqs in place of conj and has the seq arg > last. > > You may be right, but so far your chosen examples support my point: > * conj is *not* a sequence fn -- it builds the type of thing passed in, not > a seq > * nth is *not* a sequence fn -- it knows about random access collections and > navigates them appropriately
Oh, I'm sorry, I naturally interpreted "sequence fn" to mean "fn that can perform a sequence operation on a sequence arg" rather than "fn that is *exclusive* to sequences and won't work on anything else". Apparently you meant the latter? Which still doesn't matter since someone operating on sequences might very well want to call nth or similar at some point. -- 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
