about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/ArchiveWrapper.cpp
diff options
context:
space:
mode:
authorScott McMurray <scottmcm@users.noreply.github.com>2020-08-03 23:18:34 -0700
committerScott McMurray <scottmcm@users.noreply.github.com>2020-08-24 13:20:25 -0700
commitc20ad72323a17bd020f2fea7b8decf93e067c161 (patch)
treee992681676988b2a615bf44c5bf416a8e74b858d /compiler/rustc_llvm/llvm-wrapper/ArchiveWrapper.cpp
parente6d85ea5cbdc376ae388e1079769b67b9eda911c (diff)
downloadrust-c20ad72323a17bd020f2fea7b8decf93e067c161.tar.gz
rust-c20ad72323a17bd020f2fea7b8decf93e067c161.zip
Stabilize Range[Inclusive]::is_empty
I would like to propose these two simple methods for stabilization:
- Knowing that a range is exhaused isn't otherwise trivial
- Clippy would like to suggest them, but had to do extra work to disable that path <https://github.com/rust-lang/rust-clippy/issues/3807> because they're unstable
- These work on `PartialOrd`, consistently with now-stable `contains`, and are thus more general than iterator-based approaches that need `Step`
- They've been unchanged for some time, and have picked up uses in the compiler
- Stabilizing them doesn't block any future iterator-based is_empty plans, as the inherent ones are preferred in name resolution
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/ArchiveWrapper.cpp')
0 files changed, 0 insertions, 0 deletions