about summary refs log tree commit diff
path: root/src/test/ui/traits/trait-inheritance-num0.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2021-02-08 07:56:04 +0000
committerbors <bors@rust-lang.org>2021-02-08 07:56:04 +0000
commit0b96f60c07896f9dac5a0ad15464fa4ab3c1437f (patch)
treea810a3c8b6015c41d77cc466feadec015204a33c /src/test/ui/traits/trait-inheritance-num0.rs
parent4940dd483a8448c0f1ef28d304fad88a9d983c4e (diff)
parent9066c736a23c24f23fb46846e80a33c02bf4ab82 (diff)
downloadrust-0b96f60c07896f9dac5a0ad15464fa4ab3c1437f.tar.gz
rust-0b96f60c07896f9dac5a0ad15464fa4ab3c1437f.zip
Auto merge of #79245 - ssomers:btree_curb_ord_bound, r=dtolnay
BTree: remove Ord bound where it is absent elsewhere

Some btree methods don't really need an Ord bound and don't have one, while some methods that more obviously don't need it, do have one.

An example of the former is `iter`, even though it explicitly exposes the work of the Ord implementation (["sorted by key"](https://doc.rust-lang.org/std/collections/struct.BTreeMap.html#method.iter) - but I'm not suggesting it should have the Ord bound). An example of the latter is `new`, which doesn't involve any keys whatsoever.
Diffstat (limited to 'src/test/ui/traits/trait-inheritance-num0.rs')
0 files changed, 0 insertions, 0 deletions