Accept any IntoIterator in choose_multiple #92
Merged
Conversation
This file contains 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
tranzystorekk
force-pushed
the
choose-intoiter
branch
2 times, most recently
from
bccecb2 to
33d568f
Compare
tranzystorekk
force-pushed
the
choose-intoiter
branch
from
33d568f to
353f891
Compare
|
Isn't this a breaking change? |
|
Only apparently, all iterators automatically implement |
|
@taiki-e My gut is telling me there is a subtlety here I'm missing, any insights here? |
|
There is a possibility of ambiguity regarding type inference, but this is considered a minor change. See RFC1105 for more. |
Merged
Sign up for free
to 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.
Accepting only
Iterators needlessly constrains the API (case in point, the clunky example withvec![...].iter()where a simple array would suffice).Shouldn't be a breaking change since all
Iterators are no-opIntoIterators.