Tracking Issue for `new_range_remainder`

[tgross35]

Feature gate: #![feature(new_range_remainder)]

This is a tracking issue for the remainder method of new std::range iterator types.

Public API

// core::range


impl<A: Step> RangeFromIter<A> {
    pub fn remainder(self) -> RangeFrom<A>;
}

impl<A: Step> RangeInclusiveIter<A> {
    pub fn remainder(self) -> Option<RangeInclusive<A>>;
}

impl<A> RangeIter<A> {
    pub fn remainder(self) -> Range<A>;
}

Steps / History

(Remember to update the S-tracking-* label when checking boxes.)

• Proposed with the new_range RFC RFC: New range types for Edition 2024 rfcs#3550
• Implementation: Add new_range_api for RFC 3550 #125751
• Final comment period (FCP)¹
• Stabilization PR

Unresolved Questions

• Making sure the exact behavior is reasonable
  • #t-libs-api/api-changes > `RangeFrom::remainder` possible panic
  • stabilize new RangeFrom type and iterator #153380 (comment)
  • What do we guarantee for RangeIter::remainder? #154443
• Usecases needed What do we guarantee for RangeIter::remainder? #154443 (comment)

See Also

• Original tracking issue Tracking Issue for new_range_api (part of RFC 3550) #125687

Footnotes

1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩