Repository navigation
Tracking Issue for new_range_remainder #154458
Description
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_rangeRFC RFC: New range types for Edition 2024 rfcs#3550 - Implementation: Add
new_range_apifor RFC 3550 #125751 - Final comment period (FCP)1
- Stabilization PR
Unresolved Questions
- Making sure the exact behavior is reasonable
- 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
Activity
Rollup merge of rust-lang#154459 - tgross35:destabilize-range-iter-re…
Auto merge of #154459 - tgross35:destabilize-range-iter-remainder, r=…
Rollup merge of rust-lang#154459 - tgross35:destabilize-range-iter-re…
Rollup merge of rust-lang#154459 - tgross35:destabilize-range-iter-re…
Auto merge of #154459 - tgross35:destabilize-range-iter-remainder, r=…