about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2024-03-22 01:07:30 +0100
committerGitHub <noreply@github.com>2024-03-22 01:07:30 +0100
commitfa99ebc7cf0bb6dcbe63f3763c02703a7f6f8fe8 (patch)
tree52d0eac7072091bb955ff7737f1f7f4055ded5f1 /compiler/rustc_codegen_llvm/src
parentf0feebb2706ea0db78ccdcf105150ffde7993f50 (diff)
parentbeb0c22c096c68fd853cf65bb44408cf0d5ac99a (diff)
downloadrust-fa99ebc7cf0bb6dcbe63f3763c02703a7f6f8fe8.tar.gz
rust-fa99ebc7cf0bb6dcbe63f3763c02703a7f6f8fe8.zip
Rollup merge of #122817 - ultrabear:ultrabear_btreedoc, r=Nilstrieb
Doc Guarantee: BTree(Set|Map):  `IntoIter` Iterate in Sorted by key Order

This Doc-only PR adds text to the IntoIterator implementation and IntoIter type for both BTreeMap and BTreeSet that states that the returned items will be in sorted-by-key order, this is a guarantee that is made by the iter() and iter_mut() methods of BTreeMap/Set and BTreeMap respectively, but not on into_iter methods or types.

I don't know how the IntoIter iteration would not be sorted by key, and I would like to rely on that behavior for my prefix_array crate.

The text appended to IntoIter documentation is based on each types respective iter() method documentation, as is the text used in the IntoIterator documentation; they are slightly inconsistent between Set/Map, but they are consistent within their own types documentation.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions