rust/tests/ui/regions/region-object-lifetime-5.stderr

error[E0515]: cannot return reference to local data `*x`
  --> $DIR/region-object-lifetime-5.rs:11:5
   |
LL |     x.borrowed()
   |     ^^^^^^^^^^^^ returns a reference to data owned by the current function

error: aborting due to previous error

For more information about this error, try `rustc --explain E0515`.
Use larger span for adjustments on method calls Currently, we use a relatively 'small' span for THIR expressions generated by an 'adjustment' (e.g. an autoderef, autoborrow, unsizing). As a result, if a borrow generated by an adustment ends up causing a borrowcheck error, for example: ```rust let mut my_var = String::new(); let my_ref = &my_var my_var.push('a'); my_ref; ``` then the span for the mutable borrow may end up referring to only the base expression (e.g. `my_var`), rather than the method call which triggered the mutable borrow (e.g. `my_var.push('a')`) Due to a quirk of the MIR borrowck implementation, this doesn't always get exposed in migration mode, but it does in many cases. This commit makes THIR building consistently use 'larger' spans for adjustment expressions The intent of this change it make it clearer to users when it's the specific way in which a variable is used (for example, in a method call) that produdes a borrowcheck error. For example, an error message claiming that a 'mutable borrow occurs here' might be confusing if it just points at a usage of a variable (e.g. `my_var`), when no `&mut` is in sight. Pointing at the entire expression should help to emphasize that the method call itself is responsible for the mutable borrow. In several cases, this makes the `#![feature(nll)]` diagnostic output match up exactly with the default (migration mode) output. As a result, several `.nll.stderr` files end up getting removed entirely. 2021-09-16 15:01:22 -05:00			error[E0515]: cannot return reference to local data `*x`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/region-object-lifetime-5.rs:11:5`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| x.borrowed()`
Use larger span for adjustments on method calls Currently, we use a relatively 'small' span for THIR expressions generated by an 'adjustment' (e.g. an autoderef, autoborrow, unsizing). As a result, if a borrow generated by an adustment ends up causing a borrowcheck error, for example: ```rust let mut my_var = String::new(); let my_ref = &my_var my_var.push('a'); my_ref; ``` then the span for the mutable borrow may end up referring to only the base expression (e.g. `my_var`), rather than the method call which triggered the mutable borrow (e.g. `my_var.push('a')`) Due to a quirk of the MIR borrowck implementation, this doesn't always get exposed in migration mode, but it does in many cases. This commit makes THIR building consistently use 'larger' spans for adjustment expressions The intent of this change it make it clearer to users when it's the specific way in which a variable is used (for example, in a method call) that produdes a borrowcheck error. For example, an error message claiming that a 'mutable borrow occurs here' might be confusing if it just points at a usage of a variable (e.g. `my_var`), when no `&mut` is in sight. Pointing at the entire expression should help to emphasize that the method call itself is responsible for the mutable borrow. In several cases, this makes the `#![feature(nll)]` diagnostic output match up exactly with the default (migration mode) output. As a result, several `.nll.stderr` files end up getting removed entirely. 2021-09-16 15:01:22 -05:00			`\| ^^^^^^^^^^^^ returns a reference to data owned by the current function`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			`error: aborting due to previous error`

update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			For more information about this error, try `rustc --explain E0515`.