rust/tests/ui/coroutine/yield-in-args.stderr

error[E0626]: borrow may still be in use when coroutine yields
  --> $DIR/yield-in-args.rs:9:13
   |
LL |     || {
   |     -- within this coroutine
LL |         let b = true;
LL |         foo(&b, yield);
   |             ^^  ----- possible yield occurs here
   |
help: add `static` to mark this coroutine as unmovable
   |
LL |     static || {
   |     ++++++

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0626`.
s/generator/coroutine/ 2023-10-19 21:46:28 +00:00			`error[E0626]: borrow may still be in use when coroutine yields`
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-in-args.rs:9:13`
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			`\|`
Explain that coroutine can be marked static And also point out the def span of the coroutine 2024-07-21 21:37:22 -04:00			`LL \| \|\| {`
			`\| -- within this coroutine`
			`LL \| let b = true;`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| foo(&b, yield);`
update tests for migrate mode by default 2019-04-22 08:40:08 +01:00			`\| ^^ ----- possible yield occurs here`
Explain that coroutine can be marked static And also point out the def span of the coroutine 2024-07-21 21:37:22 -04:00			`\|`
			help: add `static` to mark this coroutine as unmovable
			`\|`
			`LL \| static \|\| {`
			`\| ++++++`
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 E0626`.