4.x: Fix PriorityQueue to not share a item ordering helper index #507
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.
The
PriorityQueue._count
field was a static field shared between all instances thePriorityQueue
of the same type argument. I can only assume this was thought as a tradeoff between having 8 more bytes per priority queue or trashing everybody else's cache who happen to be prioritizing on the same type argument.This PR simply changes it to a per instance counter and also removes the
Interlocked.Increment
as the class itself is by no means thread-safe so it makes no sense to have the creation of a fresh index atomic inEnqueue
.