Tracking Issue for `new_range_remainder`

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 https://github.com/rust-lang/rfcs/pull/3550
• Implementation: https://github.com/rust-lang/rust/pull/125751
• Final comment period (FCP)^1
• Stabilization PR

Unresolved Questions

• Making sure the exact behavior is reasonable
  • #t-libs-api/api-changes > `RangeFrom::remainder` possible panic
  • https://github.com/rust-lang/rust/pull/153380#issuecomment-4107709935
  • https://github.com/rust-lang/rust/issues/154443+
• Usecases needed https://github.com/rust-lang/rust/issues/154443#issuecomment-4170798339

See Also

• Original tracking issue https://github.com/rust-lang/rust/issues/125687

Start with the public API and the implementation PR #125751, then review the unresolved behavior links, including issues #154443 and #154443+. Done means resolving the behavior and use-case questions, completing the final comment period, and producing a stabilization PR.