rust/src/test/ui/nll/issue-31567.stderr

error[E0713]: borrow may still be in use when destructor runs
  --> $DIR/issue-31567.rs:12:26
   |
LL | fn get_dangling<'a>(v: VecWrapper<'a>) -> &'a u32 {
   |                 -- lifetime `'a` defined here
LL |     let s_inner: &'a S = &*v.0; //~ ERROR borrow may still be in use when destructor runs [E0713]
   |                  -----   ^^^^^
   |                  |
   |                  type annotation requires that `*v.0` is borrowed for `'a`
LL |     &s_inner.0
LL | }
   | - here, drop of `v` needs exclusive access to `*v.0`, because the type `VecWrapper<'_>` implements the `Drop` trait

error: aborting due to previous error

For more information about this error, try `rustc --explain E0713`.
Updates to tests reflecting the diangostic changes in previous commit. It is worth pointing out that the reason that so few diagnostics are effected is because of the filter I put in where it only goes down the new path if the borrowed place is not a prefix of the dropped place. (Without that filter, a lot of the tests would need this change, and it would probably be a net loss for the UX, since you'd see it even in cases like borrows of generic types where there is no explicit mention of `Drop`.) 2018-09-17 18:52:31 -05:00			`error[E0713]: borrow may still be in use when destructor runs`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-31567.rs:12:26`
add regression tests for various MIR bugs that get fixed Fixes #31567 Fixes #47470 Fixes #48132 Fixes #48179 2018-02-27 15:14:41 -06:00			`\|`
Use new region infer errors for explaining borrows This gives at least some explanation for why a borrow is expected to last for a certain free region. Also: * Reports E0373: "closure may outlive the current function" with NLL. * Special cases the case of returning a reference to (or value referencing) a local variable or temporary (E0515). * Special case assigning a reference to a local variable in a closure to a captured variable. 2018-10-14 09:12:02 -05:00			`LL \| fn get_dangling<'a>(v: VecWrapper<'a>) -> &'a u32 {`
			\| -- lifetime `'a` defined here
Updates to tests reflecting the diangostic changes in previous commit. It is worth pointing out that the reason that so few diagnostics are effected is because of the filter I put in where it only goes down the new path if the borrowed place is not a prefix of the dropped place. (Without that filter, a lot of the tests would need this change, and it would probably be a net loss for the UX, since you'd see it even in cases like borrows of generic types where there is no explicit mention of `Drop`.) 2018-09-17 18:52:31 -05:00			`LL \| let s_inner: &'a S = &*v.0; //~ ERROR borrow may still be in use when destructor runs [E0713]`
Use new region infer errors for explaining borrows This gives at least some explanation for why a borrow is expected to last for a certain free region. Also: * Reports E0373: "closure may outlive the current function" with NLL. * Special cases the case of returning a reference to (or value referencing) a local variable or temporary (E0515). * Special case assigning a reference to a local variable in a closure to a captured variable. 2018-10-14 09:12:02 -05:00			`\| ----- ^^^^^`
			`\| \|`
			\| type annotation requires that `*v.0` is borrowed for `'a`
add regression tests for various MIR bugs that get fixed Fixes #31567 Fixes #47470 Fixes #48132 Fixes #48179 2018-02-27 15:14:41 -06:00			`LL \| &s_inner.0`
			`LL \| }`
Updates to tests reflecting the diangostic changes in previous commit. It is worth pointing out that the reason that so few diagnostics are effected is because of the filter I put in where it only goes down the new path if the borrowed place is not a prefix of the dropped place. (Without that filter, a lot of the tests would need this change, and it would probably be a net loss for the UX, since you'd see it even in cases like borrows of generic types where there is no explicit mention of `Drop`.) 2018-09-17 18:52:31 -05:00			\| - here, drop of `v` needs exclusive access to `*v.0`, because the type `VecWrapper<'_>` implements the `Drop` trait
add regression tests for various MIR bugs that get fixed Fixes #31567 Fixes #47470 Fixes #48132 Fixes #48179 2018-02-27 15:14:41 -06:00
			`error: aborting due to previous error`

Updates to tests reflecting the diangostic changes in previous commit. It is worth pointing out that the reason that so few diagnostics are effected is because of the filter I put in where it only goes down the new path if the borrowed place is not a prefix of the dropped place. (Without that filter, a lot of the tests would need this change, and it would probably be a net loss for the UX, since you'd see it even in cases like borrows of generic types where there is no explicit mention of `Drop`.) 2018-09-17 18:52:31 -05:00			For more information about this error, try `rustc --explain E0713`.