os-rust/tests/ui/nll/closure-move-spans.stderr

error[E0382]: use of moved value: `x`
  --> $DIR/closure-move-spans.rs:7:13
   |
LL | fn move_after_move(x: String) {
   |                    - move occurs because `x` has type `String`, which does not implement the `Copy` trait
LL |     || x;
   |     -- - variable moved due to use in closure
   |     |
   |     value moved into closure here
LL |     let y = x;
   |             ^ value used here after move
   |
help: consider cloning the value if the performance cost is acceptable
   |
LL |     || x.clone();
   |         ++++++++

error[E0382]: borrow of moved value: `x`
  --> $DIR/closure-move-spans.rs:12:13
   |
LL | fn borrow_after_move(x: String) {
   |                      - move occurs because `x` has type `String`, which does not implement the `Copy` trait
LL |     || x;
   |     -- - variable moved due to use in closure
   |     |
   |     value moved into closure here
LL |     let y = &x;
   |             ^^ value borrowed here after move
   |
help: consider cloning the value if the performance cost is acceptable
   |
LL |     || x.clone();
   |         ++++++++

error[E0382]: borrow of moved value: `x`
  --> $DIR/closure-move-spans.rs:17:13
   |
LL | fn borrow_mut_after_move(mut x: String) {
   |                          ----- move occurs because `x` has type `String`, which does not implement the `Copy` trait
LL |     || x;
   |     -- - variable moved due to use in closure
   |     |
   |     value moved into closure here
LL |     let y = &mut x;
   |             ^^^^^^ value borrowed here after move
   |
help: consider cloning the value if the performance cost is acceptable
   |
LL |     || x.clone();
   |         ++++++++

error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0382`.
Tests for closure spans 2018-08-01 20:40:06 +01:00			error[E0382]: use of moved value: `x`
Better account for more cases involving closures 2024-04-12 04:46:31 +00:00			`--> $DIR/closure-move-spans.rs:7:13`
Tests for closure spans 2018-08-01 20:40:06 +01: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-02 16:43:08 -08: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 10:40:56 +03:00			\| - move occurs because `x` has type `String`, which does not implement the `Copy` trait
Tests for closure spans 2018-08-01 20:40:06 +01:00			`LL \| \|\| x;`
			`\| -- - variable moved due to use in closure`
			`\| \|`
			`\| value moved into closure here`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| let y = x;`
Tests for closure spans 2018-08-01 20:40:06 +01:00			`\| ^ value used here after move`
Better account for more cases involving closures 2024-04-12 04:46:31 +00:00			`\|`
			`help: consider cloning the value if the performance cost is acceptable`
			`\|`
			`LL \| \|\| x.clone();`
			`\| ++++++++`
Tests for closure spans 2018-08-01 20:40:06 +01:00
			error[E0382]: borrow of moved value: `x`
Better account for more cases involving closures 2024-04-12 04:46:31 +00:00			`--> $DIR/closure-move-spans.rs:12:13`
Tests for closure spans 2018-08-01 20:40:06 +01: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-02 16:43:08 -08: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 10:40:56 +03:00			\| - move occurs because `x` has type `String`, which does not implement the `Copy` trait
Tests for closure spans 2018-08-01 20:40:06 +01:00			`LL \| \|\| x;`
			`\| -- - variable moved due to use in closure`
			`\| \|`
			`\| value moved into closure here`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| let y = &x;`
Tests for closure spans 2018-08-01 20:40:06 +01:00			`\| ^^ value borrowed here after move`
Better account for more cases involving closures 2024-04-12 04:46:31 +00:00			`\|`
			`help: consider cloning the value if the performance cost is acceptable`
			`\|`
			`LL \| \|\| x.clone();`
			`\| ++++++++`
Tests for closure spans 2018-08-01 20:40:06 +01:00
			error[E0382]: borrow of moved value: `x`
Better account for more cases involving closures 2024-04-12 04:46:31 +00:00			`--> $DIR/closure-move-spans.rs:17:13`
Tests for closure spans 2018-08-01 20:40:06 +01: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-02 16:43:08 -08: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 10:40:56 +03:00			\| ----- move occurs because `x` has type `String`, which does not implement the `Copy` trait
Tests for closure spans 2018-08-01 20:40:06 +01:00			`LL \| \|\| x;`
			`\| -- - variable moved due to use in closure`
			`\| \|`
			`\| value moved into closure here`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| let y = &mut x;`
Tests for closure spans 2018-08-01 20:40:06 +01:00			`\| ^^^^^^ value borrowed here after move`
Better account for more cases involving closures 2024-04-12 04:46:31 +00:00			`\|`
			`help: consider cloning the value if the performance cost is acceptable`
			`\|`
			`LL \| \|\| x.clone();`
			`\| ++++++++`
Tests for closure spans 2018-08-01 20:40:06 +01:00
			`error: aborting due to 3 previous errors`

			For more information about this error, try `rustc --explain E0382`.