rust/tests/ui/nll/issue-46036.stderr

error[E0597]: `a` does not live long enough
  --> $DIR/issue-46036.rs:8:24
   |
LL |     let a = 3;
   |         - binding `a` declared here
LL |     let foo = Foo { x: &a };
   |                        ^^
   |                        |
   |                        borrowed value does not live long enough
   |                        this usage requires that `a` is borrowed for `'static`
LL |     loop { }
LL | }
   | - `a` dropped here while still borrowed

error: aborting due to previous error

For more information about this error, try `rustc --explain E0597`.
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			error[E0597]: `a` does not live long enough
Remove feature(nll) when compare mode is sufficient 2019-04-07 10:07:36 -05:00			`--> $DIR/issue-46036.rs:8:24`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\|`
Tweak E0597 CC #99430 2023-01-14 21:06:44 -06:00			`LL \| let a = 3;`
			\| - binding `a` declared here
Update tests 2019-03-09 06:03:44 -06:00			`LL \| let foo = Foo { x: &a };`
Use new region infer errors for explaining borrows This gives at least some explanation for why a borrow is expected to last for a certain free region. Also: * Reports E0373: "closure may outlive the current function" with NLL. * Special cases the case of returning a reference to (or value referencing) a local variable or temporary (E0515). * Special case assigning a reference to a local variable in a closure to a captured variable. 2018-10-14 09:12:02 -05:00			`\| ^^`
			`\| \|`
			`\| borrowed value does not live long enough`
Add `ConstraintCategory::Usage` for handling aggregate construction In some cases, we emit borrowcheck diagnostics pointing at a particular field expression in a struct expression (e.g. `MyStruct { field: my_expr }`). However, this behavior currently relies on us choosing the `ConstraintCategory::Boring` with the 'correct' span. When adding additional variants to `ConstraintCategory`, (or changing existing usages away from `ConstraintCategory::Boring`), the current behavior can easily get broken, since a non-boring constraint will get chosen over a boring one. To make the diagnostic output less fragile, this commit adds a `ConstraintCategory::Usage` variant. We use this variant for the temporary assignments created for each field of an aggregate we are constructing. Using this new variant, we can emit a message mentioning "this usage", emphasizing the fact that the error message is related to the specific use site (in the struct expression). This is preparation for additional work on improving NLL error messages (see #57374) 2021-09-06 16:59:24 -05:00			\| this usage requires that `a` is borrowed for `'static`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`LL \| loop { }`
			`LL \| }`
Don't match on region kinds when reporting NLL errors With NLL region kinds are always ReVar 2018-07-22 10:02:31 -05:00			\| - `a` dropped here while still borrowed
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0597`.