diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2022-06-01 23:36:52 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-06-01 23:36:52 +0900 |
| commit | 2c3a8cf0a465705bd010f8952961b9768d1b684e (patch) | |
| tree | 134d2a7af7e7ee836a7d96cd403ffb559a1217c8 /compiler/rustc_mir_transform/src/coverage/debug.rs | |
| parent | a7bd0d0e07ae1c5c680a32ecf2b5e5556c6935f6 (diff) | |
| parent | b02146a370e8e07186d4bd2c264699300ca925df (diff) | |
| download | rust-2c3a8cf0a465705bd010f8952961b9768d1b684e.tar.gz rust-2c3a8cf0a465705bd010f8952961b9768d1b684e.zip | |
Rollup merge of #97611 - azdavis:master, r=Dylan-DPC
Tweak insert docs
For `{Hash, BTree}Map::insert`, I always have to take a few extra seconds to think about the slight weirdness about the fact that if we "did not" insert (which "sounds" false), we return true, and if we "did" insert, (which "sounds" true), we return false.
This tweaks the doc comments for the `insert` methods of those types (as well as what looks like a rustc internal data structure that I found just by searching the codebase for "If the set did") to first use the "Returns whether _something_" pattern used in e.g. `remove`, where we say that `remove` "returns whether the value was present".
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/debug.rs')
0 files changed, 0 insertions, 0 deletions