Peter Jaszkowiak ffea65bf61 add new_range_api for RFC 3550 ...

This includes a `From<legacy::RangeInclusive> for RangeInclusive` impl for convenience, instead of the `TryFrom` impl from the RFC.
Having `From` is highly convenient and the assertion is unlikely to be a problem in practice.

This includes re-exports of all existing `Range` types under `core::range`, plus the range-related traits (`RangeBounds`, `Step`, `OneSidedRange`) and the `Bound` enum.

Currently the iterators are just wrappers around the old range types,
and most other trait impls delegate to the old rage types as well.

Also includes an `.iter()` shorthand for `.clone().into_iter()`

2024-07-05 16:33:58 -06:00

..

exclusive-range-patterns-2021.rs

…

exclusive-range-patterns-2021.stderr

…

impossible_range.fixed

…

impossible_range.rs

…

impossible_range.stderr

…

issue-54505-no-literals.fixed

…

issue-54505-no-literals.rs

…

issue-54505-no-literals.stderr

…

issue-54505-no-std.rs

…

issue-54505-no-std.stderr

…

issue-54505.fixed

…

issue-54505.rs

…

issue-54505.stderr

…

issue-73553-misinterp-range-literal.rs

…

issue-73553-misinterp-range-literal.stderr

…

range_inclusive.rs

…

range_traits-1.rs

…

range_traits-1.stderr

…

range_traits-2.rs

…

range_traits-2.stderr

…

range_traits-3.rs

…

range_traits-3.stderr

…

range_traits-4.rs

…

range_traits-5.rs

…

range_traits-6.rs

…

range_traits-6.stderr

…

range_traits-7.rs

…

range-1.rs

…

range-1.stderr

…

range-inclusive-pattern-precedence2.rs

…

range-inclusive-pattern-precedence2.stderr

…

range-inclusive-pattern-precedence.fixed

…

range-inclusive-pattern-precedence.rs

…

range-inclusive-pattern-precedence.stderr

…

range-pattern-out-of-bounds-issue-68972.rs

…

range-pattern-out-of-bounds-issue-68972.stderr

…