diff options
| author | bors <bors@rust-lang.org> | 2023-09-25 03:50:59 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-09-25 03:50:59 +0000 |
| commit | 8c04c0631719803c99e52db7301586125d30e54a (patch) | |
| tree | d212cc99cdd4b7b40b874236d33c97f9b41978e1 /compiler/rustc_mir_transform/src/coverage/counters.rs | |
| parent | 5105b1ec58d61cfeae375d88c30d7f40d7ac0c6a (diff) | |
| parent | 0f248d8ea9403850cd3d80b370fcc9b6793f17b1 (diff) | |
| download | rust-8c04c0631719803c99e52db7301586125d30e54a.tar.gz rust-8c04c0631719803c99e52db7301586125d30e54a.zip | |
Auto merge of #116074 - fzs111:clarify-pin-docs, r=Mark-Simulacrum
Clarify example in `Pin::new_unchecked` docs This example in the docs of `Pin::new_unchecked` puzzled me for a relatively long time. Now I understand that it comes down to the difference between dropping the `Pin` vs dropping the pinned value. I have extended the explanation to highlight this difference. In my opinion it is clearer now, and I hope it helps others understand `Pin` better.
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/counters.rs')
0 files changed, 0 insertions, 0 deletions