rust/tests/ui/issues/issue-42796.stderr

error[E0382]: borrow of moved value: `s`
  --> $DIR/issue-42796.rs:18:20
   |
LL |     let s = "Hello!".to_owned();
   |         - move occurs because `s` has type `String`, which does not implement the `Copy` trait
LL |     let mut s_copy = s;
   |                      - value moved here
...
LL |     println!("{}", s);
   |                    ^ value borrowed here after move
   |
   = note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider cloning the value if the performance cost is acceptable
   |
LL |     let mut s_copy = s.clone();
   |                       ++++++++

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 08:40:08 +01:00			error[E0382]: borrow of moved value: `s`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-42796.rs:18:20`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
update tests for migrate mode by default 2019-04-22 08:40:08 +01:00			`LL \| let s = "Hello!".to_owned();`
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 10:40:56 +03:00			\| - move occurs because `s` has type `String`, which does not implement the `Copy` trait
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`LL \| let mut s_copy = s;`
update tests for migrate mode by default 2019-04-22 08:40:08 +01:00			`\| - value moved here`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`...`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| println!("{}", s);`
update tests for migrate mode by default 2019-04-22 08:40:08 +01:00			`\| ^ value borrowed here after move`
Fix a format_args span to be expansion 2021-10-21 09:01:16 -05:00			`\|`
Mention first and last macro in backtrace 2022-06-20 19:25:52 -07:00			= note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
Suggest `.clone()` or `ref binding` on E0382 2022-11-02 21:22:24 -07:00			`help: consider cloning the value if the performance cost is acceptable`
			`\|`
			`LL \| let mut s_copy = s.clone();`
			`\| ++++++++`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
			`error: aborting due to previous error`

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