Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Error for ExactlyOneError, change interals of it a bit #484

Merged
merged 4 commits into from Sep 29, 2020
Merged

Implement Error for ExactlyOneError, change interals of it a bit #484

merged 4 commits into from Sep 29, 2020

Conversation

Xaeroxe
Copy link
Contributor

@Xaeroxe Xaeroxe commented Sep 22, 2020

Fixes #482

@jswrenn
Copy link
Member

jswrenn commented Sep 22, 2020

Looks like Error is std-only.

@jswrenn jswrenn added this to the next milestone Sep 22, 2020
@Xaeroxe
Copy link
Contributor Author

Xaeroxe commented Sep 24, 2020

CI failure is unrelated to this PR

src/ziptuple.rs Outdated Show resolved Hide resolved
@Xaeroxe Xaeroxe changed the title Implement Error for ExactlyOneError, change interals of it a bit, and fix a warning in ziptuple Implement Error for ExactlyOneError, change interals of it a bit Sep 29, 2020
@Xaeroxe
Copy link
Contributor Author

Xaeroxe commented Sep 29, 2020

@jswrenn this is ready for review.

Copy link
Member

@jswrenn jswrenn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bors r+

@bors
Copy link
Contributor

bors bot commented Sep 29, 2020

Build succeeded:

@bors bors bot merged commit 4114081 into rust-itertools:master Sep 29, 2020
@Xaeroxe Xaeroxe deleted the exactly_one_fixup branch September 29, 2020 20:38
Philippe-Cholet added a commit to Philippe-Cholet/itertools that referenced this pull request Jan 23, 2024
It could be derived. It apparently was decided not to in rust-itertools#484, probably to not leak implementation details that could confuse the user.
However, it would not render well for pretty formats such as `"{:#?}"`. I think we should call methods on `f` instead of using `write!`.
github-merge-queue bot pushed a commit that referenced this pull request Jan 24, 2024
It could be derived. It apparently was decided not to in #484, probably to not leak implementation details that could confuse the user.
However, it would not render well for pretty formats such as `"{:#?}"`. I think we should call methods on `f` instead of using `write!`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should 'ExactlyOneError' implement std-'Error'?
2 participants