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

ConsTuples: remove DoubleEndedIterator implementation #853

Merged

Conversation

Philippe-Cholet
Copy link
Member

@Philippe-Cholet Philippe-Cholet commented Jan 16, 2024

Fixes #852

Breaking change or simple bugfix?

@Philippe-Cholet Philippe-Cholet added this to the next milestone Jan 16, 2024
@phimuemue
Copy link
Member

@jswrenn could you merge this (or veto if you think we should fix it)?

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.

I think we should consider the removal of a trait impl to be a breaking change, even if it's the case that that impl did not behave correctly. There may be consumers who are happy with the buggy behavior, and who would be severely inconvenienced if they could no longer satisfy a DoubleEndedIterator trait bound in generic code.

Let's merge this at the same time as #835.

@Philippe-Cholet Philippe-Cholet removed this from the next milestone Jan 22, 2024
@Philippe-Cholet Philippe-Cholet added this to the next milestone Jan 30, 2024
@Philippe-Cholet Philippe-Cholet added this pull request to the merge queue Jan 30, 2024
Merged via the queue into rust-itertools:master with commit 8f33b9d Jan 30, 2024
9 checks passed
@Philippe-Cholet Philippe-Cholet deleted the cons-tuples-one-end-fix branch January 30, 2024 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ConsTuples::next_back is plain wrong
3 participants