Adjust the capacity computation in Maps.newHashMapWithExpectedSize
.
#5980
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adjust the capacity computation in
Maps.newHashMapWithExpectedSize
.This JDK change fixed the computation used when the first write to a
HashMap
isputAll(otherMap)
. Previously that would occasionally lead to an unnecessarily large internal table. That same computation was copied intoMaps.newHashMapWithExpectedSize
, so it should also be adjusted.Thanks to @XenoAmess for both the JDK fix and the fix here.
Closes #5965.
RELNOTES=
Maps.newHashMapWithExpectedSize
sometimes allocated maps that were larger than they needed to be.