improve TaskItem hashcode #8988
Merged
Conversation
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
ladipro
approved these changes
Jul 3, 2023
YuliiaKovalova
approved these changes
Jul 4, 2023
This was referenced Jul 29, 2025
Closed
Closed
This was referenced Oct 15, 2025
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Tiny improvement to the hash code calculation perf - ItemSpec is just EscapingUtilities.UnescapeAll(_includeEscaped), which is a simple deterministic transform so we can just use the string.
Added a comment to explain why we can't easily hash in something about the metadata. This means that all items with the same item spec continue to have the same hash code, which can cause degenerate performance.