Stabilize core::range::{legacy, RangeFull, RangeTo}#156629
Open
tgross35 wants to merge 2 commits into
Open
Conversation
Newly stable API:
core::range::legacy
Collaborator
|
r? @nnethercote rustbot has assigned @nnethercote. Use Why was this reviewer chosen?The reviewer was selected based on:
|
Contributor
Author
|
r? libs This API isn't covered by the FCP on the tracking issue: @rustbot label +I-libs-api-nominated |
This comment has been minimized.
This comment has been minimized.
Stabilized under `new_range_api_exports`. Newly stable API:
core::range::RangeFull;
core::range::RangeTo;
66c5493 to
8d9f3da
Compare
Collaborator
|
The job Click to see the possible cause of the failure (guessed by this bot) |
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.
Stabilize
core::range::legacyand the re-exports of unchanged range types, so all range types can now be imported from withincore::range. Newly stable API:Compared to what is in the comment, I made a few exclusions:
new_range_api(part of RFC 3550) #125687 (comment), @sendittothenewts suggested not to stabilizecore::range::RangeBoundsin case we want to reuse that name for a replacement based onIntoBounds. I have excluded it here so we can discuss further.range_into_boundstracking issue: Tracking Issue forrange_into_bounds#136903one_sided_rangetypes should probably just move into this module rather than being exported, since they are unstable. Added an unresolved question at Tracking Issue for OneSidedRange #69780.step_traitis unstable so we could just movecrate::iter::Stepifcore::rangeis a better home. Added an unresolved question at Tracking issue forstep_traitstabilization #42168.Since this is the last thing in
new_range_apithat isn't tracked elsewhere:Closes: #125687
Cc @pitaj