Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the documentation for move about Fn traits implementations #75162

Merged
merged 2 commits into from
Aug 9, 2020

Conversation

poliorcetics
Copy link
Contributor

Fixes #74997.

This uses the note from the reference but I can also just put a link to it or do both.

@rusbot modify labels: C-bug T-doc T-libs

@rust-highfive
Copy link
Collaborator

r? @joshtriplett

(rust_highfive has picked a reviewer for you, use r? to override)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 4, 2020
@poliorcetics
Copy link
Contributor Author

poliorcetics commented Aug 4, 2020

@rustbot modify labels: C-bug, T-doc, T-libs

Edit: Is rustbot dead ?

@rustbot rustbot added C-bug Category: This is a bug. A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. labels Aug 4, 2020
@jyn514
Copy link
Member

jyn514 commented Aug 8, 2020

Maybe also add the example from the forum? https://users.rust-lang.org/t/move-and-impl-fn/46660/2

Until I read that I didn't realize what this was trying to say.

@poliorcetics
Copy link
Contributor Author

@jyn514 Done, is it clearer this way ?

@jyn514
Copy link
Member

jyn514 commented Aug 8, 2020

Yeah, that helps :) I was thinking about it as 'if it's captured by value you can only use it once' but of course if you only use the reference, the value isn't dropped in the closure body.

@bors r+ rollup

@bors
Copy link
Contributor

bors commented Aug 8, 2020

📌 Commit 1cd8dff has been approved by jyn514

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Aug 8, 2020
bors added a commit to rust-lang-ci/rust that referenced this pull request Aug 8, 2020
Rollup of 15 pull requests

Successful merges:

 - rust-lang#74712 (Update E0271 explanation)
 - rust-lang#74842 (adjust remaining targets)
 - rust-lang#75151 (Consistent variable name alloc for raw_vec)
 - rust-lang#75162 (Fix the documentation for move about Fn traits implementations)
 - rust-lang#75248 (Add `as_mut_ptr` to `NonNull<[T]>`)
 - rust-lang#75262 (Show multi extension example for Path in doctests)
 - rust-lang#75266 (Add safety section to `NonNull::as_*` method docs)
 - rust-lang#75284 (Show relative example for Path ancestors)
 - rust-lang#75285 (Separate example for Path strip_prefix)
 - rust-lang#75287 (Show Path extension example change multi extension)
 - rust-lang#75288 (Use assert! for Path exists example to check bool)
 - rust-lang#75289 (Remove ambiguity from PathBuf pop example)
 - rust-lang#75290 (fix `min_const_generics` version)
 - rust-lang#75291 (Clean up E0750)
 - rust-lang#75292 (Clean up E0502)

Failed merges:

r? @ghost
@bors bors merged commit ccffe18 into rust-lang:master Aug 9, 2020
@poliorcetics poliorcetics deleted the move-documentation-fix branch August 9, 2020 12:39
@cuviper cuviper added this to the 1.47.0 milestone May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools C-bug Category: This is a bug. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Misdocumented move keyword: move closures are *not* “represented by the FnOnce trait”
8 participants