[Foundation] Update hashing for bridged NSError protocols #21056
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.
Protocols that wish to provide a default implementation of hashing should do so by providing a
hash(into:)
implementation.hashValue
has been deprecated as aHashable
requirement in SE-0206.Protocol extensions that only implement hashValue force
hashValue
-based synthesis on conforming types by default, which will probably produce deprecation warnings soon.Add missing Hashable requirements to
_BridgedNSError
and_BridgedStoredNSError
.It is important to add these extensions now, since the presence/absence of defaulted Hashable requirements can cause ABI headaches down the road for conforming types, and these protocols are
used by ClangImporterinvolved in automatic conformance synthesis.rdar://problem/46496484