rust/tests/ui/coroutine/ref-escapes-but-not-over-yield.stderr

error[E0521]: borrowed data escapes outside of coroutine
  --> $DIR/ref-escapes-but-not-over-yield.rs:11:9
   |
LL |     let mut a = &3;
   |         ----- `a` declared here, outside of the coroutine body
...
LL |         a = &b;
   |         ^^^^--
   |         |   |
   |         |   borrow is only valid in the coroutine body
   |         reference to `b` escapes the coroutine body here

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0521`.
s/generator/coroutine/ 2023-10-19 16:46:28 -05:00			`error[E0521]: borrowed data escapes outside of coroutine`
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`--> $DIR/ref-escapes-but-not-over-yield.rs:11:9`
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 05:52:49 -05:00			`\|`
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`LL \| let mut a = &3;`
s/generator/coroutine/ 2023-10-19 16:46:28 -05:00			\| ----- `a` declared here, outside of the coroutine body
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`...`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| a = &b;`
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`\| ^^^^--`
			`\| \| \|`
s/generator/coroutine/ 2023-10-19 16:46:28 -05:00			`\| \| borrow is only valid in the coroutine body`
			\| reference to `b` escapes the coroutine body here
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 05:52:49 -05:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06: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 05:52:49 -05:00
Update ui tests 2021-02-01 11:23:12 -06:00			For more information about this error, try `rustc --explain E0521`.