Make sure that concurrent map usage is thread-safe #46536
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.
Behavior upon missing prefix partial name may cause a key to overwrite when executed in multiple threads at the same time.
ref ruby-concurrency/concurrent-ruby#970
Motivation / Background
Same as here: #46534
But since guidelines state to isolate PRs, hence the second one.
Detail
This Pull Request changes the way a cache miss is handled. It makes it thread safe and ensures that it's not ovewritten in the middle of execution.
Additional information
ref: #46534
ref: ruby-concurrency/concurrent-ruby#970
Checklist
[Fix #issue-number]