rust/src/test/ui/generator/ref-escapes-but-not-over-yield.stderr

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

error: aborting due to previous error
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`error[E0521]: borrowed data escapes outside of generator`
			`--> $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;`
			\| ----- `a` is declared here, outside of the generator body
			`...`
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			`\| ^^^^--`
			`\| \| \|`
			`\| \| borrow is only valid in the generator body`
			\| reference to `b` escapes the generator 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
			`error: aborting due to previous error`