rust/src/test/ui/generator/yield-while-ref-reborrowed.stderr

error[E0501]: cannot borrow `x` as immutable because previous closure requires unique access
  --> $DIR/yield-while-ref-reborrowed.rs:36:20
   |
LL |     let mut b = || {
   |                 -- closure construction occurs here
LL |         let a = &mut *x;
   |                       - previous borrow occurs due to use of `x` in closure
...
LL |     println!("{}", x);
   |                    ^ borrow occurs here
LL |     Pin::new(&mut b).resume();
LL | }
   | - borrow from closure ends here

error: aborting due to previous error

For more information about this error, try `rustc --explain E0501`.
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[E0501]: cannot borrow `x` as immutable because previous closure requires unique access
Change generator trait to use pinning 2018-10-04 13:49:38 -05:00			`--> $DIR/yield-while-ref-reborrowed.rs:36: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			`\| -- closure construction occurs here`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| let a = &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 05:52:49 -05:00			\| - previous borrow occurs due to use of `x` in closure
			`...`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| println!("{}", 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 05:52:49 -05:00			`\| ^ borrow occurs here`
Change generator trait to use pinning 2018-10-04 13:49:38 -05:00			`LL \| Pin::new(&mut b).resume();`
Update UI tests 2018-02-22 18:42:32 -06: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 05:52:49 -05:00			`\| - borrow from closure ends here`

			`error: aborting due to previous error`

update tests 2018-03-03 08:59:40 -06:00			For more information about this error, try `rustc --explain E0501`.