os-rust/tests/ui/coroutine/yield-while-ref-reborrowed.stderr

error[E0501]: cannot borrow `x` as immutable because previous closure requires unique access
  --> $DIR/yield-while-ref-reborrowed.rs:39:20
   |
LL |     || {
   |     -- coroutine construction occurs here
LL |         let a = &mut *x;
   |                      -- first borrow occurs due to use of `x` in coroutine
...
LL |     println!("{}", x);
   |                    ^ second borrow occurs here
LL |     Pin::new(&mut b).resume(());
   |              ------ first borrow later used here
   |
   = note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0501`.
change how we report `err_out_of_scope` borrowck errors Also, remove the explicit code detecting borrows over a yield. It turns out not to be necessary -- any such borrow winds up with a lifetime that is part of the generator type, and therefore which will outlive the generator expression itself, which yields an `err_out_of_scope`. So instead we intercept those errors and display them in a nicer way. 2017-07-15 06:52:49 -04:00			error[E0501]: cannot borrow `x` as immutable because previous closure requires unique access
Error on using `yield` without also using `#[coroutine]` on the closure And suggest adding the `#[coroutine]` to the closure 2024-04-11 13:15:34 +00:00			`--> $DIR/yield-while-ref-reborrowed.rs:39:20`
change how we report `err_out_of_scope` borrowck errors Also, remove the explicit code detecting borrows over a yield. It turns out not to be necessary -- any such borrow winds up with a lifetime that is part of the generator type, and therefore which will outlive the generator expression itself, which yields an `err_out_of_scope`. So instead we intercept those errors and display them in a nicer way. 2017-07-15 06:52:49 -04:00			`\|`
Error on using `yield` without also using `#[coroutine]` on the closure And suggest adding the `#[coroutine]` to the closure 2024-04-11 13:15:34 +00:00			`LL \| \|\| {`
			`\| -- coroutine construction occurs here`
Update UI tests 2018-02-23 03:42:32 +03:00			`LL \| let a = &mut *x;`
s/generator/coroutine/ 2023-10-19 21:46:28 +00:00			\| -- first borrow occurs due to use of `x` in coroutine
change how we report `err_out_of_scope` borrowck errors Also, remove the explicit code detecting borrows over a yield. It turns out not to be necessary -- any such borrow winds up with a lifetime that is part of the generator type, and therefore which will outlive the generator expression itself, which yields an `err_out_of_scope`. So instead we intercept those errors and display them in a nicer way. 2017-07-15 06:52:49 -04:00			`...`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| println!("{}", x);`
update tests for migrate mode by default 2019-04-22 08:40:08 +01:00			`\| ^ second borrow occurs here`
Add a resume type parameter to `Generator` 2020-01-25 20:03:10 +01:00			`LL \| Pin::new(&mut b).resume(());`
update tests for migrate mode by default 2019-04-22 08:40:08 +01:00			`\| ------ first borrow later used here`
Fix a format_args span to be expansion 2021-10-21 09:01:16 -05:00			`\|`
Mention first and last macro in backtrace 2022-06-20 19:25:52 -07:00			= note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
change how we report `err_out_of_scope` borrowck errors Also, remove the explicit code detecting borrows over a yield. It turns out not to be necessary -- any such borrow winds up with a lifetime that is part of the generator type, and therefore which will outlive the generator expression itself, which yields an `err_out_of_scope`. So instead we intercept those errors and display them in a nicer way. 2017-07-15 06:52:49 -04: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`
change how we report `err_out_of_scope` borrowck errors Also, remove the explicit code detecting borrows over a yield. It turns out not to be necessary -- any such borrow winds up with a lifetime that is part of the generator type, and therefore which will outlive the generator expression itself, which yields an `err_out_of_scope`. So instead we intercept those errors and display them in a nicer way. 2017-07-15 06:52:49 -04:00
update tests 2018-03-03 15:59:40 +01:00			For more information about this error, try `rustc --explain E0501`.