add new_range_api for RFC 3550 · model-checking/verify-rust-std@d8965d3 (original) (raw)

Skip to content

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Commit d8965d3

add new_range_api for RFC 3550

This includes a `Fromlegacy::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()`

File tree

6 files changed

lines changed

6 files changed

lines changed

Lines changed: 2 additions & 0 deletions

Original file line number Diff line number Diff line change
@@ -395,6 +395,8 @@ pub mod panicking;
395 395 #[unstable(feature = "core_pattern_types", issue = "none")]
396 396 pub mod pat;
397 397 pub mod pin;
398 +#[unstable(feature = "new_range_api", issue = "125687")]
399 +pub mod range;
398 400 pub mod result;
399 401 pub mod sync;
400 402