about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2021-08-01 21:45:30 +0000
committerbors <bors@rust-lang.org>2021-08-01 21:45:30 +0000
commitcd5a90fb14bb8cb2276d9740925c9858ea507429 (patch)
treef369667a81b372f8ecd0942c3cab4fbb87f69c2a /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
parent2827db2b137e899242e81f1beea39ae26e245153 (diff)
parent35d02e2c6a081dfbe2f24b0b9608920f90f42c8a (diff)
downloadrust-cd5a90fb14bb8cb2276d9740925c9858ea507429.tar.gz
rust-cd5a90fb14bb8cb2276d9740925c9858ea507429.zip
Auto merge of #86031 - ssomers:btree_lazy_iterator, r=Mark-Simulacrum
BTree: lazily locate leaves in rangeless iterators

BTree iterators always locate both the first and last leaf edge and often only need either one, i.e., whenever they are traversed in a single direction, like in for-loops and in the common use of `iter().next()` or `iter().next_back()` to retrieve the first or last key/value-pair (#62924). It's fairly easy to avoid because the iterators with this disadvantage already are quite separate from other iterators.

r? `@Mark-Simulacrum`
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions