rust/tests/ui/codemap_tests/tab_3.stderr

error[E0382]: borrow of moved value: `some_vec`
  --> $DIR/tab_3.rs:7:20
   |
LL |     let some_vec = vec!["hi"];
   |         -------- move occurs because `some_vec` has type `Vec<&str>`, which does not implement the `Copy` trait
LL |     some_vec.into_iter();
   |              ----------- `some_vec` moved due to this method call
LL |     {
LL |         println!("{:?}", some_vec);
   |                          ^^^^^^^^ value borrowed here after move
   |
note: `into_iter` takes ownership of the receiver `self`, which moves `some_vec`
  --> $SRC_DIR/core/src/iter/traits/collect.rs:LL:COL
   = note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
help: you can `clone` the value and consume it, but this might not be your desired behavior
   |
LL |     some_vec.clone().into_iter();
   |             ++++++++

error: aborting due to previous error

For more information about this error, try `rustc --explain E0382`.
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			error[E0382]: borrow of moved value: `some_vec`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/tab_3.rs:7:20`
Fix mispositioned error indicators Fixes #38384 Most of the Rust community uses 4 spaces for indentation, but there are also tab users of Rust (including myself!). This patch fixes a bug in error printing which mispositions error indicators when near code with tabs. The code attempted to fix the issue by replacing spaces with tabs, but it sadly wasn't enough, as sometimes you may not print spaces but _ or ^ instead. This patch employs the reverse strategy: it replaces each tab with a space, so that the number of _ and ^ and spaces in error indicators below the code snippet line up perfectly. In a study [1] preceeding this patch, we could see that this strategy is also chosen by gcc version 6.3.0. Its not perfect, as the output is not beautiful, but its the easiest to implement. If anyone wants to improve on this, be my guest! This patch is meant as improvement of the status quo, not as perfect end status. It fixes the actual issue of mispositioning error indicators. [1]: https://github.com/rust-lang/rust/issues/38384#issuecomment-326813710 2017-09-07 01:47:13 -05:00			`\|`
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`LL \| let some_vec = vec!["hi"];`
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 `some_vec` has type `Vec<&str>`, which does not implement the `Copy` trait
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| some_vec.into_iter();`
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 12:48:46 -05:00			\| ----------- `some_vec` moved due to this method call
Update UI tests 2018-02-24 17:01:39 -06:00			`LL \| {`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| println!("{:?}", some_vec);`
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`\| ^^^^^^^^ value borrowed 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 12:48:46 -05:00			`\|`
Clarify what "this" means 2022-12-12 06:07:09 -06:00			note: `into_iter` takes ownership of the receiver `self`, which moves `some_vec`
mv std libs to library/ 2020-06-11 21:31:49 -05:00			`--> $SRC_DIR/core/src/iter/traits/collect.rs:LL:COL`
Mention first and last macro in backtrace 2022-06-20 21:25:52 -05:00			= note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
Create new inference context 2022-12-25 18:51:11 -06:00			help: you can `clone` the value and consume it, but this might not be your desired behavior
			`\|`
			`LL \| some_vec.clone().into_iter();`
Don't use method span on clone suggestion 2023-06-22 15:40:49 -05:00			`\| ++++++++`
Fix mispositioned error indicators Fixes #38384 Most of the Rust community uses 4 spaces for indentation, but there are also tab users of Rust (including myself!). This patch fixes a bug in error printing which mispositions error indicators when near code with tabs. The code attempted to fix the issue by replacing spaces with tabs, but it sadly wasn't enough, as sometimes you may not print spaces but _ or ^ instead. This patch employs the reverse strategy: it replaces each tab with a space, so that the number of _ and ^ and spaces in error indicators below the code snippet line up perfectly. In a study [1] preceeding this patch, we could see that this strategy is also chosen by gcc version 6.3.0. Its not perfect, as the output is not beautiful, but its the easiest to implement. If anyone wants to improve on this, be my guest! This patch is meant as improvement of the status quo, not as perfect end status. It fixes the actual issue of mispositioning error indicators. [1]: https://github.com/rust-lang/rust/issues/38384#issuecomment-326813710 2017-09-07 01:47:13 -05:00
			`error: aborting due to previous error`

update tests 2018-03-03 08:59:40 -06:00			For more information about this error, try `rustc --explain E0382`.