user0/rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Rollup merge of #70690 - GuillaumeGomez:cleanup-e0501, r=Dylan-DPC

Browse source 
Clean up E0501 explanation

r? @Dylan-DPC
This commit is contained in:
Dylan DPC 2020-04-07 00:31:38 +02:00 • committed by GitHub
commit 7500bcfbb2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

20
src/librustc_error_codes/error_codes/E0501.md
View file

@ -1,12 +1,4 @@
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.
Note that a capture will either move or borrow a variable, but in this
situation, the closure is borrowing the variable. Take a look at the chapter
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 used but it is already captured by a closure.
Erroneous code example:
@ -29,6 +21,16 @@ fn foo(a: &mut i32) {
}
```
This error indicates that a mutable variable is used while it is still captured
by a closure. Because the closure has borrowed the variable, it is not available
until the closure goes out of scope.
Note that a capture will either move or borrow a variable, but in this
situation, the closure is borrowing the variable. Take a look at the chapter
on [Capturing][capturing] in Rust By Example for more information.
[capturing]: https://doc.rust-lang.org/stable/rust-by-example/fn/closures/capture.html
To fix this error, you can finish using the closure before using the captured
variable: