The new ticket CLJ-1065 has a patch that I think implements the desired behavior on the dev wiki page.
i.e. set/map literals with duplicates are invalid (status quo) All constructor functions for sets and maps allow duplicates, and for maps, always take the value associated with the last occurrence of the same key. All constructor functions explicitly say this in their doc strings. Andy On Sep 7, 2012, at 2:06 PM, Rich Hickey wrote: > > On Sep 7, 2012, at 3:35 PM, Sean Corfield wrote: > >> On Fri, Sep 7, 2012 at 10:49 AM, Rich Hickey <richhic...@gmail.com> wrote: >>> I've added my feedback there >>> (http://dev.clojure.org/display/design/Allow+duplicate+map+keys+and+set+elements) >> >> Thanx Rich! So the recommendation is: >> >> * set/map literals with duplicates are invalid (status quo) >> >> * hash-set/hash-map should change (to last key wins, as if conj'd/assoc'd) >> >> * sorted-set/sorted-map should not change (last key wins, as if >> conj'd/assoc'd) >> >> * array-map should not change (throws on dupes)? >> >> Highlighting that last one since it's not mentioned on the wiki and >> would then be the "odd one out" but perhaps there's a good reason? > > No, array-map should be the same too. -- 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
