Just throwing in my vote here (assuming anyone's keeping count): I agree with Mark that the current behavior is surprising and disagreeable.
And while there's clearly a practical argument to be made from both perspectives, my own feeling is that throwing a hard runtime exception here is excessive and therefore un-Clojure-like behavior. Granted, that's obviously highly subjective ;) Anyway, I think he's done a good job of teasing apart some of the apparent history behind the current approach - and it seems to me that there are clearer advantages in removing this error than in keeping it. I appreciate that Clojure generally gives developers the benefit of the doubt, and I guess this feels to me like a place where that is possibly being given up for apparently no major benefit. So barring any further revelations, yes to this: Put hash maps and hash sets back to the way they were -- they worked > perfectly fine. Use the duplicate key check in ArrayMap to make ArrayMaps > behave like all the other maps, i.e., last instance of a key wins. Cheers :) - Peter Taoussanis (@ptaoussanis) -- 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
