Possible HashMap update

Paul Sandoz paul.sandoz at oracle.com
Wed Aug 14 10:34:09 UTC 2013

On Aug 14, 2013, at 12:18 PM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
> On 13/08/2013 22:18, Joe Darcy wrote:
>> Have you seen the patch from Dan Smith which would revolve all the javac lint warnings in HashMap?
>> http://mail.openjdk.java.net/pipermail/core-libs-dev/2013-August/019618.html 
> My preference would be to get Doug's update in as soon as we can, mostly because the changes are significant and it would be good to get them well exercised (and the performance/memory characterized too) before jdk8 starts to get locked down. I know the javac lint warnings are important but it's lower risk and at least some of the code in the lint patch will be replaced. I would expect it would be straight-forward to sort out any remaining issues later.


If no one else volunteers i can try and sort this out and sync up stuff from the current HashMap/LinkedHashMap (e.g. forEachRem. as reported by Remi) and the lint warnings in one go, and submit for review. 

I do have a vested interest since it fixes another bug related to the incorrect reporting of splitrerator characteristics in LInkedHashMap (they should report ORDERED).


More information about the core-libs-dev mailing list