On 19/02/2013 05:27, Mike Duigou wrote:
:
http://cr.openjdk.java.net/~mduigou/JDK-7197183/0/
From our current testing we found that applications currently using subSequence() failed
if the equals(), hashCode() and toString() implementations did not exactly match String.
Additionally we had to change String.equals() so that it recognizes can return
"true" for matching instances of String.SubSequence.
I'm not sure about this either, especially with String.equals clearly
specifying that the argument must be a String.
The updates to AbstractStringBuilder append and insert seems unrelated,
I assume you did measurements. Just wondering about separating them out
as a separate patch?
-Alan
