mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e4b9f86054
rust/tests/ui/async-await/issue-76547.stderr

33 lines
1.2 KiB
Plaintext
Raw Normal View History

add nll compare mode stderr file
2020-11-09 18:27:15 -06:00
error: lifetime may not live long enough
Fully stabilize NLL
2022-04-01 12:13:25 -05:00
--> $DIR/issue-76547.rs:20:13
add nll compare mode stderr file
2020-11-09 18:27:15 -06:00
|
LL | async fn fut(bufs: &mut [&mut [u8]]) {
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
| - - let's call the lifetime of this reference `'2`
| |
| let's call the lifetime of this reference `'1`
LL | ListFut(bufs).await
| ^^^^ this usage requires that `'1` must outlive `'2`
Make lifetime errors more precise in the presence of `Fresh` lifetimes.
2022-05-12 14:25:38 -05:00
|
help: consider introducing a named lifetime parameter
|
LL | async fn fut<'a>(bufs: &'a mut [&'a mut [u8]]) {
| ++++ ++ ++
add nll compare mode stderr file
2020-11-09 18:27:15 -06:00
error: lifetime may not live long enough
Fully stabilize NLL
2022-04-01 12:13:25 -05:00
--> $DIR/issue-76547.rs:34:14
add nll compare mode stderr file
2020-11-09 18:27:15 -06:00
|
LL | async fn fut2(bufs: &mut [&mut [u8]]) -> i32 {
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
| - - let's call the lifetime of this reference `'2`
| |
| let's call the lifetime of this reference `'1`
LL | ListFut2(bufs).await
| ^^^^ this usage requires that `'1` must outlive `'2`
Make lifetime errors more precise in the presence of `Fresh` lifetimes.
2022-05-12 14:25:38 -05:00
|
help: consider introducing a named lifetime parameter
|
LL | async fn fut2<'a>(bufs: &'a mut [&'a mut [u8]]) -> i32 {
| ++++ ++ ++
add nll compare mode stderr file
2020-11-09 18:27:15 -06:00
error: aborting due to 2 previous errors
Reference in New Issue Copy Permalink