Change _stringsByHashCode to store the string. #12127
Merged
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.
Fixes #
Context
The
WeakStringCacheused to store all the strings in the same dictionary, but was recently switched to use separate collections to store the longer strings that are held by weak references vs shorter strings that always used a string reference. In both cases, aStringWeakHandledwas allocated to track the value in the dictionary. This is only needed when we use a handle to track larger strings, so we can avoid the allocation in most cases and simplifyStringWeakHandlesince it no longer has to potentially store a strong reference to a string. This saves ~20MB of allocations when building Roslyn.Before:

After:

Changes Made
Testing
Notes