rust/tests/ui/disallowed-deconstructing/disallowed-deconstructing-destructing-struct-let.stderr

error[E0509]: cannot move out of type `X`, which implements the `Drop` trait
  --> $DIR/disallowed-deconstructing-destructing-struct-let.rs:13:22
   |
LL |     let X { x: y } = x;
   |                -     ^ cannot move out of here
   |                |
   |                data moved here
   |                move occurs because `y` has type `String`, which does not implement the `Copy` trait
   |
help: consider borrowing the pattern binding
   |
LL |     let X { x: ref y } = x;
   |                +++

error: aborting due to previous error

For more information about this error, try `rustc --explain E0509`.
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			error[E0509]: cannot move out of type `X`, which implements the `Drop` trait
Suggest `ref` for some patterns as a fallback 2022-12-08 19:14:56 -06:00			`--> $DIR/disallowed-deconstructing-destructing-struct-let.rs:13:22`
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 \| let X { x: y } = x;`
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`\| - ^ cannot move out of here`
			`\| \|`
			`\| data moved here`
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 `y` has type `String`, which does not implement the `Copy` trait
Suggest `ref` for some patterns as a fallback 2022-12-08 19:14:56 -06:00			`\|`
			`help: consider borrowing the pattern binding`
			`\|`
			`LL \| let X { x: ref y } = x;`
			`\| +++`
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 E0509`.