[Proposal] Conform Never to Equatable and Hashable
#855
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
BasThomas
reviewed
May 26, 2018
|
|
||
| ## Alternatives considered | ||
| ### Make `Never` conform to _all_ protocols | ||
| As a bottom type, `Never` could conceivably to every protocol automatically. This would have some advantages and might be ideal, but would require a lot more work to determine the design and implement the behavior. |
There was a problem hiding this comment.
could conceivably conform* to
mdiep
force-pushed
the
conform-never-to-equatable-and-hashable
branch
from
1cdc3cf to
b0e16d9
Compare
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.
Swift-evolution thread