diff options
| author | bors <bors@rust-lang.org> | 2018-05-25 22:18:27 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2018-05-25 22:18:27 +0000 |
| commit | 07c415c2154f29d6dce8da0154ef41c8a5497fbf (patch) | |
| tree | 28953c14cf6541f651c295f9815ae4c2aa5614d9 /src/rustllvm/RustWrapper.cpp | |
| parent | 990d8aa743b1dda3cc0f68fe09524486261812c6 (diff) | |
| parent | f7c4a33f32b8139778b8c6792b9e55c74770a234 (diff) | |
| download | rust-07c415c2154f29d6dce8da0154ef41c8a5497fbf.tar.gz rust-07c415c2154f29d6dce8da0154ef41c8a5497fbf.zip | |
Auto merge of #51033 - coryshrmn:master, r=dtolnay
stabilize RangeBounds collections_range #30877 The FCP for #30877 closed last month, with the decision to: 1. move from `collections::range::RangeArgument` to `ops::RangeBounds`, and 2. rename `start()` and `end()` to `start_bounds()` and `end_bounds()`. Simon Sapin already moved it to `ops::RangeBounds` in #49163. I renamed the functions, and removed the old `collections::range::RangeArgument` alias. This is my first Rust PR, please let me know if I can improve anything. This passes all tests for me, except the `clippy` tool (which uses `RangeArgument::start()`). I considered deprecating `start()` and `end()` instead of removing them, but the contribution guidelines indicate we can break `clippy` temporarily. I thought it was best to remove the functions, since we're worried about name collisions with `Range::start` and `end`. Closes #30877.
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
