os-rust/tests/ui/nll/issue-40510-1.stderr

error: captured variable cannot escape `FnMut` closure body
  --> $DIR/issue-40510-1.rs:7:9
   |
LL |     let mut x: Box<()> = Box::new(());
   |         ----- variable defined here
LL |
LL |     || {
   |      - inferred to be a `FnMut` closure
LL |         &mut x
   |         ^^^^^-
   |         |    |
   |         |    variable captured here
   |         returns a reference to a captured variable which escapes the closure body
   |
   = note: `FnMut` closures only have access to their captured variables while they are executing...
   = note: ...therefore, they cannot allow references to captured variables to escape

error: aborting due to 1 previous error
Change compare mode to use -Zborrowck=mir 2019-01-27 11:03:21 +00:00			error: captured variable cannot escape `FnMut` closure body
Adjust & --bless tests due to no longer downgrading NLL errors on 2015. 2019-09-06 15:47:50 +02:00			`--> $DIR/issue-40510-1.rs:7:9`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
Display information about captured variable in `FnMut` error Fixes #69446 When we encounter a region error involving an `FnMut` closure, we display a specialized error message. However, we currently do not tell the user which upvar was captured. This makes it difficult to determine the cause of the error, especially when the closure is large. This commit records marks constraints involving closure upvars with `ConstraintCategory::ClosureUpvar`. When we decide to 'blame' a `ConstraintCategory::Return`, we additionall store the captured upvar if we found a `ConstraintCategory::ClosureUpvar` in the path. When generating an error message, we point to relevant spans if we have closure upvar information available. We further customize the message if an `async` closure is being returned, to make it clear that the captured variable is being returned indirectly. 2020-05-23 21:40:55 -04:00			`LL \| let mut x: Box<()> = Box::new(());`
			`\| ----- variable defined here`
fix one more case of trailing space 2022-06-08 21:07:59 +03:00			`LL \|`
Use span of the closure args in free region errors 2018-08-05 14:33:38 +01:00			`LL \| \|\| {`
Improve errors for `FnMut` closures. This commit improves the errors for `FnMut` closures where a reference to a captured variable is escaping. 2018-10-04 01:50:23 +02:00			\| - inferred to be a `FnMut` closure
Use span of the closure args in free region errors 2018-08-05 14:33:38 +01:00			`LL \| &mut x`
Display information about captured variable in `FnMut` error Fixes #69446 When we encounter a region error involving an `FnMut` closure, we display a specialized error message. However, we currently do not tell the user which upvar was captured. This makes it difficult to determine the cause of the error, especially when the closure is large. This commit records marks constraints involving closure upvars with `ConstraintCategory::ClosureUpvar`. When we decide to 'blame' a `ConstraintCategory::Return`, we additionall store the captured upvar if we found a `ConstraintCategory::ClosureUpvar` in the path. When generating an error message, we point to relevant spans if we have closure upvar information available. We further customize the message if an `async` closure is being returned, to make it clear that the captured variable is being returned indirectly. 2020-05-23 21:40:55 -04:00			`\| ^^^^^-`
			`\| \| \|`
			`\| \| variable captured here`
			`\| returns a reference to a captured variable which escapes the closure body`
Use span of the closure args in free region errors 2018-08-05 14:33:38 +01:00			`\|`
Improve errors for `FnMut` closures. This commit improves the errors for `FnMut` closures where a reference to a captured variable is escaping. 2018-10-04 01:50:23 +02:00			= note: `FnMut` closures only have access to their captured variables while they are executing...
			`= note: ...therefore, they cannot allow references to captured variables to escape`
Change compare mode to use -Zborrowck=mir 2019-01-27 11:03:21 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Update output for borrowck=migrate compare mode. This commit updates the test output for the updated NLL compare mode that uses `-Z borrowck=migrate` rather than `-Z borrowck=mir`. The previous commit changes `compiletest` and this commit only updates `.nll.stderr` files. 2018-10-17 00:57:32 +02:00