Uh oh!
There was an error while loading. Please reload this page.
derive PartialEq and Eq for ParseCharError - #47790
Merged
Merged
Conversation
unlike the other Parse*Error types, ParseCharError didn't have these implemented for whatever reason
rust-highfive
commented
Jan 26, 2018
Contributor
r? @sfackler (rust_highfive has picked a reviewer for you, use r? to override) |
kennytm
commented
Jan 31, 2018
Member
Review ping @sfackler! |
emilyalbini
commented
Feb 5, 2018
Member
@sfackler this PR awaits your review :) |
sfackler
commented
Feb 9, 2018
Member
Oops, sorry about the delay! @bors r+ |
bors
commented
Feb 9, 2018
Collaborator
📌 Commit 838ddbf has been approved by |
kennytm
commented
Feb 9, 2018
Member
@bors rollup |
kennytm added a commit
to kennytm/rust
that referenced
this pull request
Feb 9, 2018
derive PartialEq and Eq for `ParseCharError` unlike the other Parse*Error types, ParseCharError didn't have these implemented for whatever reason
kennytm added a commit
to kennytm/rust
that referenced
this pull request
Feb 9, 2018
derive PartialEq and Eq for `ParseCharError` unlike the other Parse*Error types, ParseCharError didn't have these implemented for whatever reason
bors added a commit
that referenced
this pull request
Feb 9, 2018
kennytm added a commit
to kennytm/rust
that referenced
this pull request
Feb 10, 2018
derive PartialEq and Eq for `ParseCharError` unlike the other Parse*Error types, ParseCharError didn't have these implemented for whatever reason
bors added a commit
that referenced
this pull request
Feb 10, 2018
bors added a commit
that referenced
this pull request
Feb 10, 2018
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 freeto 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.
unlike the other Parse*Error types, ParseCharError didn't have these implemented for whatever reason