On Sun, Aug 5, 2012 at 1:42 PM, Mark Engelberg <mark.engelb...@gmail.com>wrote:
> 3. People may differ about which flavor constructor the literals should > use, but I don't see any arguments here warranting a breaking change. Also, although it was a breaking change to add throw-on-duplicate behavior to many types of maps and sets, reverting back to 1.2 behavior could not possibly be a "breaking change" in the literal sense. Anyone whose code works right now on 1.4, by definition, has no duplicate keys. Therefore, relaxing the restriction on duplicate keys can't possibly affect their existing code and cause it to break. So it's not really fair to use the label "breaking change" to resist rollback and punt on making an informed decision as to which flavor is more appropriate for literals and/or the most common constructors. If your desire is conservatism, the safest thing is to rollback this change, because it will protect people upgrading from 1.2, without affecting 1.4 users at all. -- 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
