rust/tests/ui/generator/yield-while-iterating.stderr

error[E0626]: borrow may still be in use when generator yields
  --> $DIR/yield-while-iterating.rs:13:18
   |
LL |         for p in &x {
   |                  ^^
LL |             yield();
   |             ------- possible yield occurs here

error[E0502]: cannot borrow `x` as immutable because it is also borrowed as mutable
  --> $DIR/yield-while-iterating.rs:58:20
   |
LL |     let mut b = || {
   |                 -- mutable borrow occurs here
LL |         for p in &mut x {
   |                       - first borrow occurs due to use of `x` in generator
...
LL |     println!("{}", x[0]);
   |                    ^ immutable borrow occurs here
LL |     Pin::new(&mut b).resume(());
   |              ------ mutable borrow later used here

error: aborting due to 2 previous errors

Some errors have detailed explanations: E0502, E0626.
For more information about an error, try `rustc --explain E0502`.
Use a free error code 2017-07-29 11:05:50 -05:00			`error[E0626]: borrow may still be in use when generator yields`
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`--> $DIR/yield-while-iterating.rs:13:18`
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 2019-03-09 06:03:44 -06:00			`LL \| for p in &x {`
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 \| yield();`
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			`\| ------- possible yield occurs here`

			error[E0502]: cannot borrow `x` as immutable because it is also borrowed as mutable
Change generator trait to use pinning 2018-10-04 13:49:38 -05:00			`--> $DIR/yield-while-iterating.rs:58: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 05:52:49 -05:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| let mut b = \|\| {`
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			`\| -- mutable borrow occurs here`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| for p in &mut x {`
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			\| - first borrow occurs due to use of `x` in generator
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 2019-03-09 06:03:44 -06:00			`LL \| println!("{}", x[0]);`
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			`\| ^ immutable borrow occurs here`
Add a resume type parameter to `Generator` 2020-01-25 13:03:10 -06:00			`LL \| Pin::new(&mut b).resume(());`
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`\| ------ mutable borrow later used 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 2 previous errors`

hide `--explain` hint if error has no extended info 2019-04-17 12:26:38 -05:00			`Some errors have detailed explanations: E0502, E0626.`
update tests 2018-03-03 08:59:40 -06:00			For more information about an error, try `rustc --explain E0502`.