On Fri, Jun 29, 2012 at 10:51 AM, Warren Lynn <wrn.l...@gmail.com> wrote: > 1. Put good documentations on the functions, and the programmer needs to > have some idea what data structure is fast/slow for what use. If the > programmer does not have a clue, why would making "last" artificially slow > on vectors help? Plus, whether one data structure is slower than the other > for certain operations can also be an implementation detail that may change.
The design choice has nothing to do with speed, it has nothing to do with concrete types like lists and vectors either, no matter what might have been said before by others. David -- 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
