rust/src/test/ui/error-codes/E0161.migrate.stderr

error[E0161]: cannot move a value of type dyn Bar: the size of dyn Bar cannot be statically determined
  --> $DIR/E0161.rs:32:5
   |
LL |     x.f();
   |     ^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0161`.
Change example and tests for E0161. The code will not emit this warning once box expressions require a sized type (since that error is emitted earlier in the flow). 2021-08-20 08:59:42 -05:00			`error[E0161]: cannot move a value of type dyn Bar: the size of dyn Bar cannot be statically determined`
Remove all migrate.nll.stderr files 2021-11-20 06:13:40 -06:00			`--> $DIR/E0161.rs:32:5`
Update E0161 test to cover more cases Update another test that broke due to E0161 no longer being buffered 2018-08-21 14:47:39 -05:00			`\|`
Change example and tests for E0161. The code will not emit this warning once box expressions require a sized type (since that error is emitted earlier in the flow). 2021-08-20 08:59:42 -05:00			`LL \| x.f();`
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			`\| ^^^^^`
Update E0161 test to cover more cases Update another test that broke due to E0161 no longer being buffered 2018-08-21 14:47:39 -05:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0161`.