You must be referring to the detection of contract violations. It shouldn't be an issue; on the contrary, that seems useful info. And those who depend on legacy or third-party code can always stick to the old behavior.
Area: API: Utilities Synopsis: Updated sort behavior for Arrays and Collections may throw an IllegalArgumentException Description: The sorting algorithm used by java.util.Arrays.sort and (indirectly) by java.util.Collections.sort has been replaced. The new sort implementation may throw an IllegalArgumentException if it detects a Comparable that violates the Comparable contract. The previous implementation silently ignored such a situation. If the previous behavior is desired, you can use the new system property, java.util.Arrays.useLegacyMergeSort, to restore previous mergesort behavior. Nature of Incompatibility: behavioral RFE: 6804124 http://www.oracle.com/technetwork/java/javase/compatibility-417013.html#source On Wednesday, September 12, 2012 5:54:22 AM UTC-7, Canonical.Chris wrote: > > Clojure's sort just trampolines down to the Java sort implementation. > Between 1.6 and 1.7, the Java guys have really cracked down on the > interface that people must satisfy with their comparators. LISP is much > looser with its sorting requirements. I just wanted to know how people felt > about these changes. -- 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
