nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-30 18:53:39 +00:00
Code Issues Packages Projects Releases Wiki Activity
489c2e9918
rust/tests/ui/nll/closure-move-spans.stderr

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

40 lines
1.4 KiB
Plaintext
Raw Normal View History

Tests for closure spans
2018-08-01 19:40:06 +00:00
error[E0382]: use of moved value: `x`
Remove feature(nll) when compare mode is sufficient
2019-04-07 15:07:36 +00:00
--> $DIR/closure-move-spans.rs:5:13
Tests for closure spans
2018-08-01 19:40:06 +00:00
|
When using value after move, point at span of local When trying to use a value after move, instead of using a note, point at the local declaration that has a type that doesn't implement `Copy` trait.
2019-01-03 00:43:08 +00:00
LL | fn move_after_move(x: String) {
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 `x` has type `String`, which does not implement the `Copy` trait
Tests for closure spans
2018-08-01 19:40:06 +00:00
LL | || x;
| -- - variable moved due to use in closure
| |
| value moved into closure here
Update tests
2019-03-09 12:03:44 +00:00
LL | let y = x;
Tests for closure spans
2018-08-01 19:40:06 +00:00
| ^ value used here after move
error[E0382]: borrow of moved value: `x`
Remove feature(nll) when compare mode is sufficient
2019-04-07 15:07:36 +00:00
--> $DIR/closure-move-spans.rs:10:13
Tests for closure spans
2018-08-01 19:40:06 +00:00
|
When using value after move, point at span of local When trying to use a value after move, instead of using a note, point at the local declaration that has a type that doesn't implement `Copy` trait.
2019-01-03 00:43:08 +00:00
LL | fn borrow_after_move(x: String) {
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 `x` has type `String`, which does not implement the `Copy` trait
Tests for closure spans
2018-08-01 19:40:06 +00:00
LL | || x;
| -- - variable moved due to use in closure
| |
| value moved into closure here
Update tests
2019-03-09 12:03:44 +00:00
LL | let y = &x;
Tests for closure spans
2018-08-01 19:40:06 +00:00
| ^^ value borrowed here after move
error[E0382]: borrow of moved value: `x`
Remove feature(nll) when compare mode is sufficient
2019-04-07 15:07:36 +00:00
--> $DIR/closure-move-spans.rs:15:13
Tests for closure spans
2018-08-01 19:40:06 +00:00
|
When using value after move, point at span of local When trying to use a value after move, instead of using a note, point at the local declaration that has a type that doesn't implement `Copy` trait.
2019-01-03 00:43:08 +00:00
LL | fn borrow_mut_after_move(mut x: String) {
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 `x` has type `String`, which does not implement the `Copy` trait
Tests for closure spans
2018-08-01 19:40:06 +00:00
LL | || x;
| -- - variable moved due to use in closure
| |
| value moved into closure here
Update tests
2019-03-09 12:03:44 +00:00
LL | let y = &mut x;
Tests for closure spans
2018-08-01 19:40:06 +00:00
| ^^^^^^ value borrowed here after move
error: aborting due to 3 previous errors
For more information about this error, try `rustc --explain E0382`.
Reference in New Issue Copy Permalink