Uh oh!
There was an error while loading. Please reload this page.
Make BTreeSet::Insert docs more consistent - #33276
Conversation
GuillaumeGomez
commented
Apr 29, 2016
Thanks! r=me @steveklabnik |
rust-highfive
commented
Apr 29, 2016
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. |
steveklabnik
commented
Apr 29, 2016
Thanks for the follow-up 😄 @bors: r=guilliaumegomez rollup |
bors
commented
Apr 29, 2016
📌 Commit 3c1d087 has been approved by |
steveklabnik
commented
Apr 29, 2016
@bors; r=GuillaumeGomez rollup |
bors
commented
Apr 29, 2016
💡 This pull request was already approved, no need to approve it again.
|
bors
commented
Apr 29, 2016
📌 Commit 3c1d087 has been approved by |
bors
commented
Apr 30, 2016
…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