http://dev.clojure.org/jira This file is an XML representation of an issue en-us 4.4 649 25-07-2011 http://dev.clojure.org/jira/browse/CLJ-1065 Clojure <p>See description here <a href="http://dev.clojure.org/display/design/Allow+duplicate+map+keys+and+set+elements">http://dev.clojure.org/display/design/Allow+duplicate+map+keys+and+set+elements</a></p> CLJ-1065

Allow duplicate set elements and map keys for all set and map constructors

Defect Minor Closed Completed Unassigned Andy Fingerhut Sat, 8 Sep 2012 01:15:16 -0500 Thu, 4 Oct 2012 10:15:06 -0500 Thu, 4 Oct 2012 10:15:06 -0500 Release 1.4 Release 1.5 0 3 <p>I think that clj-1065-set-map-constructors-allow-duplicates-v1.txt dated Sep 7 2012 updates Clojure for the behavior Rich recommends on the dev Wiki page in the description. I may have missed something, though. Perhaps the most questionable part is the way I've chosen to implement array-map always taking the last key's value. It is no less efficient than the PersistentArrayMap createWithCheck method, i.e. O(n^2). </p> <p>Thanks!</p> <p>array-map is ok. I would prefer that the docs strings say "as if by repeated assoc" (or conj for sets). "eliminates" and "last" are less precise e.g. what if you pass equal things, but with different metadata, to hash-set? "Eliminates dupes" doesn't say.</p> <p>clj-1065-set-map-constructors-allow-duplicates-v2.txt dated Sep 8 2012 supersedes yesterday's -v1.txt patch, which I will remove.</p> <p>This one updates doc strings per Rich's suggestion.</p> <p>Also, his mention of metadata and "as if by assoc" led me to beef up the new test cases to check that metadata is correct, and I thus found that my new array-map constructor was not doing the right thing. This one does.</p> <p>There is still no implementation of Rich's #3 yet. Just wanted to get this one up there in case someone else builds on it before I do.</p> <p>Patch clj-1065-do-map-constant-duplicate-key-checks-compile-time-only-v1.txt only makes changes that should eliminate run-time checks for duplicate map keys, if they are compile-time constants.</p> <p>It is currently separate from the changes to those for the set/map constructor functions, since I am less sure about these changes. I'm not terribly familiar with the compiler internals, and I might be going about this the wrong way. Better to get separate feedback on these changes alone. I'm happy to merge them all into one patch if both parts look good.</p> Approval Ok Global Rank Patch Code and Test