[SE-0143] Amend to explicitly allow conditional conformances to Hashable #808
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.
Following discussions on this forum thread, amend SE-0143 to explicitly include the adoption of conditional conformances for
Hashable
by the following types:Optional
Array
ArraySlice
ContiguousArray
Dictionary
Range
ClosedRange
This involves a little bit more work than
Equatable
: while we could make use of existing implementations of==
forEquatable
, none of these types currently implementhashValue
.The above list intentionally does not include types whose
Hashable
implementation is even remotely controversial (such asSlice
,AnyCollection
orAnySequence
), or that don't already implementEquatable
(such asCollectionOfOne
orDictionaryLiteral
).A draft implementation is available in swiftlang/swift#14527. (It is being updated in parallel to this PR; a version that's in line with this amendment will be available soon.)Update: See swiftlang/swift#15382 for the implementation.