-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BTree: improve public descriptions and comments #91749
Conversation
Hm, elements feels like a not significant improvement over values, I feel like it's easy to read that as values, not the keys -- maybe something like "key-value pairs" is more clear cut? |
I don't understand what you mean at all. But I didn't look beyond math and btree.
If you agree "values" is confusing, obvious names are "elements" or "keys". "key-value pairs" makes no sense to me - it's |
Ah, I think I somehow intuited this was modifying both map and set. For set I agree elements seems good, apologies for the confusion. @bors r+ rollup |
📌 Commit 27b4b19 has been approved by |
…askrgr Rollup of 5 pull requests Successful merges: - rust-lang#91086 (Implement `TryFrom<&'_ mut [T]>` for `[T; N]`) - rust-lang#91091 (Stabilize `ControlFlow::{is_break, is_continue}`) - rust-lang#91749 (BTree: improve public descriptions and comments) - rust-lang#91819 (rustbot: Add autolabeling for `T-compiler`) - rust-lang#91824 (Make `(*mut T)::write_bytes` `const`) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
BTreeSet has always used the term "value" next to and meaning the same thing as "elements" (in the mathematical sense but also used for key-value pairs in BTreeMap), while in the BTreeMap sense these "values" are known as "keys" and definitely not "values". Today I had enough of that.
r? @Mark-Simulacrum