nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-12-03 12:13:43 +00:00
Code Issues Packages Projects Releases Wiki Activity
49691b1f70
rust/tests/ui/issues/issue-64559.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

23 lines
910 B
Plaintext
Raw Normal View History

Fix the span used to suggest avoiding for-loop moves It was using the snippet from the "use" span, which often renders the same, but with closures that snippet is on the start of the closure where the value is captured. We should be using the snippet from the span where it was moved into the `for` loop, which is `move_span`.
2019-09-20 23:06:32 +00:00
error[E0382]: use of moved value: `orig`
--> $DIR/issue-64559.rs:4:20
|
LL | let orig = vec![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 07:40:56 +00:00
| ---- move occurs because `orig` has type `Vec<bool>`, which does not implement the `Copy` trait
Fix the span used to suggest avoiding for-loop moves It was using the snippet from the "use" span, which often renders the same, but with closures that snippet is on the start of the closure where the value is captured. We should be using the snippet from the span where it was moved into the `for` loop, which is `move_span`.
2019-09-20 23:06:32 +00:00
LL | for _val in orig {}
Tweak move error Point at method definition that causes type to be consumed. Fix #94056.
2022-03-02 04:30:16 +00:00
| ---- `orig` moved due to this implicit call to `.into_iter()`
Fix the span used to suggest avoiding for-loop moves It was using the snippet from the "use" span, which often renders the same, but with closures that snippet is on the start of the closure where the value is captured. We should be using the snippet from the span where it was moved into the `for` loop, which is `move_span`.
2019-09-20 23:06:32 +00:00
LL | let _closure = || orig;
| ^^ ---- use occurs due to use in closure
| |
| value used here after move
Explain move errors that occur due to method calls involving `self` This is a re-attempt of #72389 (which was reverted in #73594) Instead of using `ExpnKind::Desugaring` to represent operators, this PR checks the lang item directly.
2020-06-11 17:48:46 +00:00
|
Clarify what "this" means
2022-12-12 12:07:09 +00:00
note: `into_iter` takes ownership of the receiver `self`, which moves `orig`
mv std libs to library/
2020-06-12 02:31:49 +00:00
--> $SRC_DIR/core/src/iter/traits/collect.rs:LL:COL
Tweak move error Point at method definition that causes type to be consumed. Fix #94056.
2022-03-02 04:30:16 +00:00
help: consider iterating over a slice of the `Vec<bool>`'s content to avoid moving into the `for` loop
|
LL | for _val in &orig {}
| +
Fix the span used to suggest avoiding for-loop moves It was using the snippet from the "use" span, which often renders the same, but with closures that snippet is on the start of the closure where the value is captured. We should be using the snippet from the span where it was moved into the `for` loop, which is `move_span`.
2019-09-20 23:06:32 +00:00
error: aborting due to previous error
For more information about this error, try `rustc --explain E0382`.
Reference in New Issue Copy Permalink