rust/src/test/ui/generator/yield-while-iterating.stderr

error[E0626]: borrow may still be in use when generator yields
  --> $DIR/yield-while-iterating.rs:13:19
   |
LL |         for p in &x { //~ ERROR
   |                   ^
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 {
   |                       - previous borrow occurs due to use of `x` in closure
...
LL |     println!("{}", x[0]); //~ ERROR
   |                    ^ immutable borrow occurs here
LL |     Pin::new(&mut b).resume();
LL | }
   | - mutable borrow ends here

error: aborting due to 2 previous errors

Some errors occurred: E0502, E0626.
For more information about an error, try `rustc --explain E0502`.
Use a free error code 2017-07-29 09:05:50 -07:00			`error[E0626]: borrow may still be in use when generator yields`
Change generator trait to use pinning 2018-10-04 20:49:38 +02:00			`--> $DIR/yield-while-iterating.rs:13:19`
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 UI tests 2018-02-23 03:42:32 +03:00			`LL \| for p in &x { //~ 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 UI tests 2018-02-23 03:42:32 +03: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 06:52:49 -04: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 20:49:38 +02: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 06:52:49 -04:00			`\|`
Update UI tests 2018-02-23 03:42:32 +03: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 06:52:49 -04:00			`\| -- mutable borrow occurs here`
Update UI tests 2018-02-23 03:42:32 +03:00			`LL \| for p in &mut x {`
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			\| - previous borrow occurs due to use of `x` in closure
			`...`
Update UI tests 2018-02-23 03:42:32 +03:00			`LL \| println!("{}", x[0]); //~ 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			`\| ^ immutable borrow occurs here`
Change generator trait to use pinning 2018-10-04 20:49:38 +02:00			`LL \| Pin::new(&mut b).resume();`
Update UI tests 2018-02-23 03:42:32 +03:00			`LL \| }`
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			`\| - mutable borrow ends here`

			`error: aborting due to 2 previous errors`

update tests 2018-03-03 15:59:40 +01:00			`Some errors occurred: E0502, E0626.`
			For more information about an error, try `rustc --explain E0502`.