diff options
| author | Jubilee <46493976+workingjubilee@users.noreply.github.com> | 2024-07-05 23:23:34 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-07-05 23:23:34 -0700 |
| commit | 9c8a88996eb9f51846fb60aa40e411ed95066fae (patch) | |
| tree | 01e92cb63a533287fdf07f1e3c72179a4829c662 /compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp | |
| parent | 51917e2e69702e5752bce6a4f3bfd285d0f4ae39 (diff) | |
| parent | ffea65bf6101ddecf14787c1a29a1460320c5a91 (diff) | |
| download | rust-9c8a88996eb9f51846fb60aa40e411ed95066fae.tar.gz rust-9c8a88996eb9f51846fb60aa40e411ed95066fae.zip | |
Rollup merge of #125751 - pitaj:new_range_api, r=jhpratt
Add `new_range_api` for RFC 3550 Initial implementation for #125687 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 debug assert should find almost all misuses. 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. Tracking issues: - https://github.com/rust-lang/rust/issues/123741 - https://github.com/rust-lang/rust/issues/125687
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp')
0 files changed, 0 insertions, 0 deletions