Skip to content

Tracking Issue for RFC 3550: New range types #123741

Open
@traviscross

Description

@traviscross

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:

About 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

Unresolved Questions

  • Will the migration cost make this feasible for either Rust 2024 or Rust 2027?
  • How do we properly document and execute the ecosystem transition?
  • How much time will it take to propagate this change throughout the ecosystem?
  • What degree of ecosystem saturation would we be satisfied with?
  • How much time do we need with stable library types before making the lang change?
  • What about libraries that wish to maintain a certain MSRV?
  • Taking into account all of the mitigations (diagnostics, migrations, and lints but NOT language-level changes), is the level of ecosystem disruption acceptable?
  • What is expected of new libraries? Should they continue to support both sets of ranges or only the new ones?
  • Will new Rust users need to learn about older editions because of downstream users of their code?
  • "Would #[cfg(overflow_checks)] just magically work?" (see here).

Related

cc @pitaj

Metadata

Metadata

Assignees

Labels

A-maybe-future-editionSomething we may consider for a future edition.B-RFC-approvedBlocker: Approved by a merged RFC but not yet implemented.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCF-new_range`#![feature(new_range)]`S-tracking-impl-incompleteStatus: The implementation is incomplete.S-tracking-needs-documentationStatus: Needs documentation.S-tracking-needs-migration-lintStatus: This item needs a migration lint.S-tracking-unimplementedStatus: The feature has not been implemented.T-langRelevant to the language team, which will review and decide on the PR/issue.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions