Fix instances of incorrectly sized Maps and Sets - #2798
Merged
bbakerman merged 1 commit intoApr 17, 2022
Conversation
kilink
force-pushed
the
incorrectly-sized-map-and-set
branch
from
April 16, 2022 18:29
fc156c3 to
532e81f
Compare
Fix a few occurrences where a Map or Set was initialized with an initial capacity value N, and then immediately filled with N items, which would always trigger a resize.
kilink
force-pushed
the
incorrectly-sized-map-and-set
branch
from
April 16, 2022 18:31
532e81f to
0569b75
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fix a few occurrences where a Map or Set was initialized with an initial capacity
value N, and then immediately filled with N items, which would always trigger
a resize.