Remove AA >: A constraint from XorT.orElse#725
Merged
Conversation
Current coverage is
|
Contributor
|
👍 |
Member
There was a problem hiding this comment.
Since we are not using xor after match I think we can just remove xor => xor match { ... }.
Contributor
Author
There was a problem hiding this comment.
Yet another good catch. I pushed an update.
Member
|
👍 |
fthomas
added a commit
that referenced
this pull request
Dec 9, 2015
Remove AA >: A constraint from XorT.orElse
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.
No description provided.