On Sat, Jun 30, 2012 at 7:09 AM, Warren Lynn <wrn.l...@gmail.com> wrote: > As I mentioned before, the issue here is not just a fast "last". The issue > here is I find the design of Clojure "wrong", or confusing. That really > shakes my confidence in the whole system.
Some of Clojure's design decisions take a while to really internalize. Several folks here have explained them but you're still not satisfied. I don't think there's much more they can do at this point. > According to the book "Clojure Programming" by Chas, one of the Clojure's > principles is to "build on abstractions" and to separate abstractions from > concrete types. Now I have a little deeper contact with Clojure and my > impression is that is not the reality. But it is the abstractions specifically that lead to the situation you are in, with last operating the way it does, as several folks have explained. Some have suggested you read through and understand the implementation of Clojure. That may help you understand the abstractions better (it may not). But, as has been stated (repeatedly) in this thread, Clojure is this way for a (good) reason. I actually think Stu's post was one of the clearest explanations... -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- 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
