Clean up E0501 explanation #70690
Merged
Clean up E0501 explanation #70690
+11
−9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rust-highfive
added
the
S-waiting-on-review
Dylan-DPC-zz
suggested changes
Apr 2, 2020
| on [Capturing][capturing] in Rust By Example for more information. | ||
|
|
||
| [capturing]: https://doc.rust-lang.org/stable/rust-by-example/fn/closures/capture.html | ||
| A mutable variable is being used whereas it has already been captured by a |
There was a problem hiding this comment.
Suggested change
| A mutable variable is being used whereas it has already been captured by a | |
| A mutable variable is used but it is already captured by a closure. |
|
|
||
| [capturing]: https://doc.rust-lang.org/stable/rust-by-example/fn/closures/capture.html | ||
| A mutable variable is being used whereas it has already been captured by a | ||
| closure. |
| @@ -29,6 +22,16 @@ fn foo(a: &mut i32) { | |||
| } | |||
| ``` | |||
|
|
|||
| This error indicates that a mutable variable is being used while it is still | |||
There was a problem hiding this comment.
Suggested change
| This error indicates that a mutable variable is being used while it is still | |
| This error indicates that a mutable variable is used while it is still |
| @@ -29,6 +22,16 @@ fn foo(a: &mut i32) { | |||
| } | |||
| ``` | |||
|
|
|||
| This error indicates that a mutable variable is being used while it is still | |||
| captured by a closure. Because the closure has borrowed the variable, it is not | |||
| available for use until the closure goes out of scope. | |||
There was a problem hiding this comment.
Suggested change
| available for use until the closure goes out of scope. | |
| available till the closure goes out of scope. |
GuillaumeGomez
force-pushed
the
cleanup-e0501
branch
from
010ae69 to
f80a380
Compare
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
GuillaumeGomez
force-pushed
the
cleanup-e0501
branch
from
f80a380 to
84c97ee
Compare
|
@bors r+ rollup |
|
📌 Commit 84c97ee has been approved by |
bors
added
S-waiting-on-bors
Dylan-DPC-zz
pushed a commit
to Dylan-DPC-zz/rust
that referenced
this pull request
Apr 6, 2020
…an-DPC Clean up E0501 explanation r? @Dylan-DPC
This was referenced Apr 6, 2020
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Apr 7, 2020
Rollup of 5 pull requests Successful merges: - rust-lang#70612 (Add io::Write::write_all_vectored) - rust-lang#70690 (Clean up E0501 explanation) - rust-lang#70821 (expose suggestions::InferCtxtExt for clippy) - rust-lang#70839 (clean up E0506 explanation) - rust-lang#70859 (Move sanitize-inline-always test to sanitize directory) Failed merges: r? @ghost
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
r? @Dylan-DPC