Tracking issue for start, end and new methods of RangeInclusive · Issue #49022 · rust-lang/rust (original) (raw)

Tracking issue for the start, end and new methods of RangeInclusive.

(Originally the tracking issue for rust-lang/rfcs#1980 the start and end fields, but we decided to make the representation private in #49022 (comment))

Steps:

• Implementation Introduce RangeInclusive::{new, start, end} methods and make the fields private. #49724
• Stabilization PR Stabilise inclusive_range_methods #50758

Unresolved questions:

• Should we want to expose the fields as public (stabilize as is), or simply provide getter methods and don't show the implementation detail (redesign from scratch)?

This issue is separated from #28237 since there were vocal oppositions from the community (see #47813) due to performance loss if we commit to the two-field design.

If you want start and end, please use these for now:

• x.start() ↦ x.next().unwrap()
• x.end() ↦ x.next_back().unwrap()