rust/tests/ui/functional-struct-update/functional-struct-update-noncopyable.stderr

error[E0509]: cannot move out of type `A`, which implements the `Drop` trait
  --> $DIR/functional-struct-update-noncopyable.rs:12:14
   |
LL |     let _b = A { y: Arc::new(3), ..a };
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^
   |              |
   |              cannot move out of here
   |              move occurs because `a.x` has type `Arc<isize>`, which does not implement the `Copy` trait
   |
help: clone the value from the field instead of using the functional record update syntax
   |
LL |     let _b = A { y: Arc::new(3), x: a.x.clone() };
   |                                ~~~~~~~~~~~~~~~~

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0509`.
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			error[E0509]: cannot move out of type `A`, which implements the `Drop` trait
update tests for migrate mode by default 2019-04-22 07:40:08 +00:00			`--> $DIR/functional-struct-update-noncopyable.rs:12:14`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| let _b = A { y: Arc::new(3), ..a };`
Update tests for changes to cannot move errors 2019-05-05 11:02:32 +00:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^`
			`\| \|`
			`\| cannot move out of 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 07:40:56 +00:00			\| move occurs because `a.x` has type `Arc<isize>`, which does not implement the `Copy` trait
Suggest `.clone()` in some move errors ``` error[E0507]: cannot move out of `x` which is behind a shared reference --> $DIR/borrowck-fn-in-const-a.rs:6:16 \| LL \| return x \| ^^ move occurs because `x` has type `String`, which does not implement the `Copy` trait \| help: consider cloning the value if the performance cost is acceptable \| LL - return x LL + return x.clone() \| ``` 2024-03-13 03:41:41 +00:00			`\|`
review comments Added comments and reworded messages 2024-04-12 20:57:07 +00:00			`help: clone the value from the field instead of using the functional record update syntax`
Suggest `.clone()` in some move errors ``` error[E0507]: cannot move out of `x` which is behind a shared reference --> $DIR/borrowck-fn-in-const-a.rs:6:16 \| LL \| return x \| ^^ move occurs because `x` has type `String`, which does not implement the `Copy` trait \| help: consider cloning the value if the performance cost is acceptable \| LL - return x LL + return x.clone() \| ``` 2024-03-13 03:41:41 +00:00			`\|`
Account for move error in the spread operator on struct literals We attempt to suggest an appropriate clone for move errors on expressions like `S { ..s }` where a field isn't `Copy`. If we can't suggest, we still don't emit the incorrect suggestion of `S { ..s }.clone()`. ``` error[E0509]: cannot move out of type `S<K>`, which implements the `Drop` trait --> $DIR/borrowck-struct-update-with-dtor.rs:28:19 \| LL \| let _s2 = S { a: 2, ..s0 }; \| ^^^^^^^^^^^^^^^^ \| \| \| cannot move out of here \| move occurs because `s0.c` has type `K`, which does not implement the `Copy` trait \| help: clone the value from the field instead of using the spread operator syntax \| LL \| let _s2 = S { a: 2, c: s0.c.clone(), ..s0 }; \| +++++++++++++++++ ``` ``` error[E0509]: cannot move out of type `S<()>`, which implements the `Drop` trait --> $DIR/borrowck-struct-update-with-dtor.rs:20:19 \| LL \| let _s2 = S { a: 2, ..s0 }; \| ^^^^^^^^^^^^^^^^ \| \| \| cannot move out of here \| move occurs because `s0.b` has type `B`, which does not implement the `Copy` trait \| note: `B` doesn't implement `Copy` or `Clone` --> $DIR/borrowck-struct-update-with-dtor.rs:4:1 \| LL \| struct B; \| ^^^^^^^^ help: if `B` implemented `Clone`, you could clone the value from the field instead of using the spread operator syntax \| LL \| let _s2 = S { a: 2, b: s0.b.clone(), ..s0 }; \| +++++++++++++++++ ``` 2024-03-16 18:19:17 +00:00			`LL \| let _b = A { y: Arc::new(3), x: a.x.clone() };`
			`\| ~~~~~~~~~~~~~~~~`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00
			For more information about this error, try `rustc --explain E0509`.