Repository navigation
Fix Result extensions ambiguity - #733
Merged
Merged
Conversation
mdiep
approved these changes
May 13, 2019
Contributor
|
Awesome, thanks! Not sure how we missed this. 🙈 |
This was referenced Jun 18, 2019
Merged
|
Just a heads up that this was a backward incompatible API change. We were using this, and our build broke after the upgrade from 6.0.0 to 6.1.0. |
Member
|
As stated at #743 (comment), this was considered as a bug. |
Merged
1 task
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Hi.
public protocol ResultProtocol,public var value: Success?&public var error: Failure?brings ambiguity for those who wrote their own extensions or use antitypical/Result.This PR attempts to fix this issue.
Checklist