Tracking Issue for RFC 3550: New range types #123741
Labels
A-edition-2024
Area: The 2024 edition
B-RFC-approved
Blocker: Approved by a merged RFC but not yet implemented.
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
F-new_range
`#![feature(new_range)]`
S-tracking-impl-incomplete
Status: The implementation is incomplete.
S-tracking-needs-documentation
Status: Needs documentation.
S-tracking-needs-migration-lint
Status: This item needs a migration lint.
S-tracking-unimplemented
Status: The feature has not been implemented.
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
This is a tracking issue for the RFC 3550: New range types
The feature gate for the issue is
#![feature(new_range)]
.Tracking issue for the library change:
new_range_api
(part of RFC 3550) #125687About tracking issues
Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps
new_range_api
for RFC 3550 #125751Unresolved Questions
Will the migration cost make this feasible for either Rust 2024 or Rust 2027?
Related
new_range_api
(part of RFC 3550) #125687new_range_api
for RFC 3550 #125751cc @pitaj
The text was updated successfully, but these errors were encountered: