fix: make SourceFileRef::Hash consistent with Eq/Ord #2199
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
bitwalker
approved these changes
Sep 22, 2025
bitwalker
added
the
no changelog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Align SourceFileRef hashing with its equality and ordering semantics by removing span from the hash and hashing only the selected string. Previously, PartialEq/Ord compared only as_str(), while Hash mixed in both span and as_str(), violating the Eq/Hash contract and risking incorrect behavior in hash-based collections. This change ensures that equal values produce identical hashes and matches the pattern used by Span.