I agree that the current throw-on-duplicates behavior is broken, because it renders literals with variable keys useless.
> 1. Simplicity is partially about having orthogonal primitives. A duplicate-removing collection factory cannot be sensibly used to implement a throw-on-duplicates collection factory, nor vice versa, so both seem equally primitive to me. Yes, but duplicate-removing is far more common. Also it's far more useful in terms of runtime behavior. Looking at the original thread, the array-map constructor should have been fixed, if anything. The part where throw-on-dupes has value, are configuration maps, which don't tend to have embedded variables. So my suggestion is: - Let the reader do duplicate checking - If people feel the need, make separate constructor with dupes check - Have our cake and eat it 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
