Closed
Conversation
575434d to
81a4c23
Compare
Member
|
Seems reasonable on a quick read. |
Member
Author
|
I'll leave it as a draft for now, we can re-evaluate this when we have a use case not covered by #278 |
Member
Author
|
It doesn't look like we're merging this soon. |
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
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.
Add a fast path alternative to
Ranges::from_iter. This makes the ranges invariants part of the API, which I think is fine because i don't expect them to change. I'm not sure if we should yet, since this is not a performance critical part really.