-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: None
-
Component/s: core-libs
-
None
-
b114
ConcurrentHashMap.Node should have a new constructor that does not take a next field. This makes callers slightly more readable, but more importantly ensures that the VM will not perform a useless volatile write of null when it's statically known that the default value of the field suffices.