diff options
| author | Stuart Cook <Zalathar@users.noreply.github.com> | 2025-08-10 19:45:54 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-10 19:45:54 +1000 |
| commit | 461009dc939327b9fcb83fe39ae07bb76987fc0f (patch) | |
| tree | 2126674713b7fbf6691491d432708f1472f43423 /tests/rustdoc-js/slice-array.js | |
| parent | a4acb8aafa34878f337ec8b656ca4e26e9834db3 (diff) | |
| parent | 06e43655bc57359ece7143d5cd31afc3a0744a59 (diff) | |
| download | rust-461009dc939327b9fcb83fe39ae07bb76987fc0f.tar.gz rust-461009dc939327b9fcb83fe39ae07bb76987fc0f.zip | |
Rollup merge of #145162 - ada4a:hash_and_btree_map-add-entry-section, r=joshtriplett
`{BTree,Hash}Map`: add "`Entry` API" section heading
I wanted to link to an introduction of the `Entry` API to the help message of `clippy::map_entry` (see https://github.com/rust-lang/rust-clippy/issues/11598 for motivation), but I found the documentation on the `Entry` enum itself a bit short. On the other hand, `{BTree,Hash}Map` both have sections in their docs introducing the whole API and giving usage examples, and so I would like to link to that instead. For that, I introduce the "`Entry` API" section heading to both of them.
Do let me know whether you think this is the right approach.
Diffstat (limited to 'tests/rustdoc-js/slice-array.js')
0 files changed, 0 insertions, 0 deletions