5 Commits

Author	SHA1	Message	Date
Peter Jaszkowiak	620e92f016	stabilize new Range type and iterator ... stabilizes `core::range::Range` stabilizes `core::range::RangeIter` stabilizes `std::range` which was missed in prior PRs Updates docs to reflect stabilization (removed "experimental") `RangeIter::remainder` is excluded from stabilization	2026-03-30 22:17:27 -06:00
Peter Jaszkowiak	d2020fbf7c	stabilize new inclusive range type and iter ... stabilizes `core::range::RangeInclusive` and `core::range::RangeInclusiveIter` and the `core::range` module	2026-02-06 21:36:15 -07:00
Trevor Gross	bb239c290c	library: Rename IterRange* to Range*Iter ... There is a weak convention in the ecosystem that `IterFoos` is an iterator yielding items of type `Foo` (e.g. `bitflags` `IterNames`, `hashbrown` `IterBuckets`), while `FooIter` is an iterator over `Foo` from an `.iter()` or `.into_iter()` method (e.g. `memchr` `OneIter`, `regex` `SetMatchesIter`). Rename `IterRange`, `IterRangeInclusive`, and `IterRangeFrom` to `RangeIter`, `RangeInclusiveIter`, and `RangeInclusiveIter` to match this. Tracking issue: RUST-125687 (`new_range_api`)	2025-12-02 16:20:50 -05:00
Jeremy Smart	8d0c07f1a1	change end to last	2025-09-08 22:07:43 -04:00
Peter Jaszkowiak	f530a29944	implement unstable new_range feature ... for RFC 3550, tracking issue #123741	2025-01-30 21:33:11 -07:00