rust/src/test/ui/use/use-after-move-implicity-coerced-object.stderr

error[E0382]: borrow of moved value: `n`
  --> $DIR/use-after-move-implicity-coerced-object.rs:28:13
   |
LL |     let n: Box<_> = Number { n: 42 }.into();
   |         - move occurs because `n` has type `Box<Number>`, which does not implement the `Copy` trait
LL |     let mut l: Box<_> = List { list: Vec::new() }.into();
LL |     l.push(n);
   |            - value moved here
LL |
LL |     let x = n.to_string();
   |             ^^^^^^^^^^^^^ value borrowed here after move

error: aborting due to previous error

For more information about this error, try `rustc --explain E0382`.
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			error[E0382]: borrow of moved value: `n`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/use-after-move-implicity-coerced-object.rs:28:13`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Remove box syntax from most places in src/test outside of the issues dir 2021-08-24 19:39:40 -05:00			`LL \| let n: Box<_> = Number { n: 42 }.into();`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 02:40:56 -05:00			\| - move occurs because `n` has type `Box<Number>`, which does not implement the `Copy` trait
Remove box syntax from most places in src/test outside of the issues dir 2021-08-24 19:39:40 -05:00			`LL \| let mut l: Box<_> = List { list: Vec::new() }.into();`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`LL \| l.push(n);`
			`\| - value moved here`
fix one more case of trailing space 2022-06-08 13:07:59 -05:00			`LL \|`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`LL \| let x = n.to_string();`
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			`\| ^^^^^^^^^^^^^ value borrowed here after move`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			`error: aborting due to previous error`

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