rust/tests/ui/moves/issue-46099-move-in-macro.stderr

error[E0382]: use of moved value: `b`
  --> $DIR/issue-46099-move-in-macro.rs:14:12
   |
LL |     let b = Box::new(true);
   |         - move occurs because `b` has type `Box<bool>`, which does not implement the `Copy` trait
LL |     test!({b});
   |            ^ value used here after move
   |
help: consider cloning the value if the performance cost is acceptable
   |
LL |     test!({b.clone()});
   |             ++++++++

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0382`.
Fix spurious 'value moved here in previous iteration of loop' messages Fixes #46099 Previously, we would check the 'move' and 'use' spans to see if we should emit this message. However, this can give false positives when macros are involved, since two distinct expressions may end up with the same span. Instead, we check the actual MIR `Location`, which eliminates false positives. 2020-06-21 20:27:34 -05:00			error[E0382]: use of moved value: `b`
			`--> $DIR/issue-46099-move-in-macro.rs:14:12`
			`\|`
			`LL \| let b = Box::new(true);`
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 `b` has type `Box<bool>`, which does not implement the `Copy` trait
Fix spurious 'value moved here in previous iteration of loop' messages Fixes #46099 Previously, we would check the 'move' and 'use' spans to see if we should emit this message. However, this can give false positives when macros are involved, since two distinct expressions may end up with the same span. Instead, we check the actual MIR `Location`, which eliminates false positives. 2020-06-21 20:27:34 -05:00			`LL \| test!({b});`
Tweak move error Point at method definition that causes type to be consumed. Fix #94056. 2022-03-01 22:30:16 -06:00			`\| ^ value used here after move`
Suggest `.clone()` or `ref binding` on E0382 2022-11-02 23:22:24 -05:00			`\|`
			`help: consider cloning the value if the performance cost is acceptable`
			`\|`
			`LL \| test!({b.clone()});`
			`\| ++++++++`
Fix spurious 'value moved here in previous iteration of loop' messages Fixes #46099 Previously, we would check the 'move' and 'use' spans to see if we should emit this message. However, this can give false positives when macros are involved, since two distinct expressions may end up with the same span. Instead, we check the actual MIR `Location`, which eliminates false positives. 2020-06-21 20:27:34 -05:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Fix spurious 'value moved here in previous iteration of loop' messages Fixes #46099 Previously, we would check the 'move' and 'use' spans to see if we should emit this message. However, this can give false positives when macros are involved, since two distinct expressions may end up with the same span. Instead, we check the actual MIR `Location`, which eliminates false positives. 2020-06-21 20:27:34 -05:00
			For more information about this error, try `rustc --explain E0382`.