-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[5.1 04-24-2019][Foundation] Modernize hashing in Foundation's Swift-only types #24369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
airspeedswift
merged 32 commits into
swiftlang:swift-5.1-branch-04-24-2019
from
lorentey:foundation-hashing-5.1-2019-04-24
Apr 30, 2019
Merged
[5.1 04-24-2019][Foundation] Modernize hashing in Foundation's Swift-only types #24369
airspeedswift
merged 32 commits into
swiftlang:swift-5.1-branch-04-24-2019
from
lorentey:foundation-hashing-5.1-2019-04-24
Apr 30, 2019
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
…*all* components The new definition diverges from the existing hashValue: it feeds all path components to the hasher, rather than just a limited subset. Hashing all the bits that are compared in == is necessary to ensure proper operation of the hash table.
This replaces the compiler-generated variant (based on hashValue) with a better implementation.
Note: URL does not implement Hashable.
I’m not sure why I was so convinced it wasn’t, but this certainly simplifies things.
…trary subset" This reverts commit b711ed9.
…bilize hashing The `ObjectIdentifier(object as AnyObject)` is not necessarily stable; this breaks reflexivity for ==, and it makes the hash encoding nondeterministic.
@swift-ci test |
airspeedswift
approved these changes
Apr 30, 2019
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.
This is cherry-picked from #23832 -- see there for an extended discussion.
This PR upgrades the Foundation overlay to use the new hashing API introduced in SE-0206. This gets rid of the deprecation warnings for
hashValue
implementations and brings the overlay in sync with current Swift best practices.Reviewed by: @itaiferber and @parkera
rdar://problem/43394032