diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2021-06-10 11:02:13 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-06-10 11:02:13 +0900 |
| commit | ceed6191946025b45b7760cecdf69104856b1fb5 (patch) | |
| tree | 1df205d2c05e961999acb3e9b22276b098b090ee /compiler/rustc_mir/src/transform/coverage/debug.rs | |
| parent | 232e7a5e7abac697c9d669cb4bb6380affa69b55 (diff) | |
| parent | 67f4f3baec8113444c20db1f8ed461fa811d09bb (diff) | |
| download | rust-ceed6191946025b45b7760cecdf69104856b1fb5.tar.gz rust-ceed6191946025b45b7760cecdf69104856b1fb5.zip | |
Rollup merge of #86051 - erer1243:update_move_keyword_docs, r=Mark-Simulacrum
Updated code examples and wording in move keyword documentation
Had a conversation with someone on the Rust Discord who was confused by the move keyword documentation. Some of the wording is odd sounding ("owned by value" - what else can something be owned by?). Also, some of the examples used Copy types when demonstrating move, leading to variables still being accessible in the outer scope after the move, contradicting the examples' comments.
I changed the move keyword documentation a bit, removing that odd wording and changing all the examples to use non-Copy types
Diffstat (limited to 'compiler/rustc_mir/src/transform/coverage/debug.rs')
0 files changed, 0 insertions, 0 deletions