[Foundation] Make CocoaError.Code and URLError.Code Hashable. #10437
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
This is consistent with imported error codes, which are always Hashable. URLError.Code was also Hashable in Swift 3.1 by virtue of being defined as an enum; the change to a struct broke that. rdar://problem/32066434
|
@swift-ci Please smoke test |
parkera
approved these changes
Jun 21, 2017
jrose-apple
added a commit
to jrose-apple/swift
that referenced
this pull request
Jun 21, 2017
…ang#10437) This is consistent with imported error codes, which are always Hashable. URLError.Code was also Hashable in Swift 3.1 by virtue of being defined as an enum; the change to a struct broke that. rdar://problem/32066434
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 consistent with imported error codes, which are always Hashable. URLError.Code was also Hashable in Swift 3.1 by virtue of being defined as an enum; the change to a struct broke that.
rdar://problem/32066434