rust/src/test/ui/issues/issue-29723.stderr

error[E0382]: use of moved value: `s`
  --> $DIR/issue-29723.rs:10:13
   |
LL |     let s = String::new();
   |         - move occurs because `s` has type `String`, which does not implement the `Copy` trait
LL |     let _s = match 0 {
LL |         0 if { drop(s); false } => String::from("oops"),
   |                     - value moved here
...
LL |             s
   |             ^ value used here after move

error: aborting due to previous error

For more information about this error, try `rustc --explain E0382`.
Add regression test for #29723 fixes #29723 2018-01-18 15:54:35 +00:00			error[E0382]: use of moved value: `s`
remove feature(nll) in more cases. 2019-09-06 14:23:00 +00:00			`--> $DIR/issue-29723.rs:10:13`
Add regression test for #29723 fixes #29723 2018-01-18 15:54:35 +00:00			`\|`
When using value after move, point at span of local When trying to use a value after move, instead of using a note, point at the local declaration that has a type that doesn't implement `Copy` trait. 2019-01-03 00:43:08 +00:00			`LL \| let s = String::new();`
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 07:40:56 +00:00			\| - move occurs because `s` has type `String`, which does not implement the `Copy` trait
When using value after move, point at span of local When trying to use a value after move, instead of using a note, point at the local declaration that has a type that doesn't implement `Copy` trait. 2019-01-03 00:43:08 +00:00			`LL \| let _s = match 0 {`
Update UI tests 2018-02-23 00:42:32 +00:00			`LL \| 0 if { drop(s); false } => String::from("oops"),`
Add regression test for #29723 fixes #29723 2018-01-18 15:54:35 +00:00			`\| - value moved here`
			`...`
Update UI tests 2018-02-23 00:42:32 +00:00			`LL \| s`
Add regression test for #29723 fixes #29723 2018-01-18 15:54:35 +00:00			`\| ^ value used here after move`

			`error: aborting due to previous error`

update tests 2018-03-03 14:59:40 +00:00			For more information about this error, try `rustc --explain E0382`.