Make BTreeSet::Insert docs more consistent #33276
Conversation
|
Thanks! r=me @steveklabnik |
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @steveklabnik (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
|
Thanks for the follow-up 😄 @bors: r=guilliaumegomez rollup |
|
📌 Commit 3c1d087 has been approved by |
|
@bors; r=GuillaumeGomez rollup |
|
💡 This pull request was already approved, no need to approve it again.
|
|
📌 Commit 3c1d087 has been approved by |
…eGomez Make BTreeSet::Insert docs more consistent Made the BTreeSet::Insert documentation consistent with the HashSet::Insert documentation by using the term 'value' instead of 'key'. r? @steveklabnik
Made the BTreeSet::Insert documentation consistent with the HashSet::Insert documentation by using the term 'value' instead of 'key'.
r? @steveklabnik