rust/tests/ui/rfcs/rfc-0107-bind-by-move-pattern-guards/rfc-reject-double-move-across-arms.stderr

error[E0507]: cannot move out of `v` in pattern guard
  --> $DIR/rfc-reject-double-move-across-arms.rs:7:36
   |
LL |         VecWrapper::A(v) if { drop(v); false } => 1,
   |                                    ^ move occurs because `v` has type `Vec<i32>`, which does not implement the `Copy` trait
   |
   = note: variables bound in patterns cannot be moved from until after the end of the pattern guard

error[E0507]: cannot move out of `v` in pattern guard
  --> $DIR/rfc-reject-double-move-across-arms.rs:15:51
   |
LL |         VecWrapper::A(v) if let Some(()) = { drop(v); None } => 1,
   |                                                   ^ move occurs because `v` has type `Vec<i32>`, which does not implement the `Copy` trait
   |
   = note: variables bound in patterns cannot be moved from until after the end of the pattern guard

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0507`.
Update tests for changes to cannot move errors 2019-05-05 06:02:32 -05:00			error[E0507]: cannot move out of `v` in pattern guard
Test the borrowck behavior of if-let guards 2022-12-21 09:29:35 -06:00			`--> $DIR/rfc-reject-double-move-across-arms.rs:7:36`
Tests for `feature(bind_by_move_pattern_guards)`. Apparently copyright notices are no longer necessary apparently. (See #43498 and #53654.) 2018-09-07 10:52:49 -05:00			`\|`
			`LL \| VecWrapper::A(v) if { drop(v); false } => 1,`
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 `v` has type `Vec<i32>`, which does not implement the `Copy` trait
Update tests for changes to cannot move errors 2019-05-05 06:02:32 -05:00			`\|`
			`= note: variables bound in patterns cannot be moved from until after the end of the pattern guard`
Tests for `feature(bind_by_move_pattern_guards)`. Apparently copyright notices are no longer necessary apparently. (See #43498 and #53654.) 2018-09-07 10:52:49 -05:00
Test the borrowck behavior of if-let guards 2022-12-21 09:29:35 -06:00			error[E0507]: cannot move out of `v` in pattern guard
			`--> $DIR/rfc-reject-double-move-across-arms.rs:15:51`
			`\|`
			`LL \| VecWrapper::A(v) if let Some(()) = { drop(v); None } => 1,`
			\| ^ move occurs because `v` has type `Vec<i32>`, which does not implement the `Copy` trait
			`\|`
			`= note: variables bound in patterns cannot be moved from until after the end of the pattern guard`

			`error: aborting due to 2 previous errors`
Tests for `feature(bind_by_move_pattern_guards)`. Apparently copyright notices are no longer necessary apparently. (See #43498 and #53654.) 2018-09-07 10:52:49 -05:00
			For more information about this error, try `rustc --explain E0507`.