rust/src/test/ui/codemap_tests/tab_3.stderr

error[E0382]: use of moved value: `some_vec`
  --> $DIR/tab_3.rs:7:20
   |
LL |     some_vec.into_iter();
   |     -------- value moved here
LL |     {
LL |         println!("{:?}", some_vec);
   |                          ^^^^^^^^ value used here after move
   |
   = note: move occurs because `some_vec` has type `std::vec::Vec<&str>`, which does not implement the `Copy` trait

error: aborting due to previous error

For more information about this error, try `rustc --explain E0382`.
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[E0382]: use 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 UI tests 2018-02-22 18:42:32 -06:00			`LL \| some_vec.into_iter();`
Display `\t` in diagnostics code as four spaces 2017-11-13 00:06:00 -06:00			`\| -------- value moved here`
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);`
Display `\t` in diagnostics code as four spaces 2017-11-13 00:06:00 -06:00			`\| ^^^^^^^^ value used here after move`
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			`\|`
			= note: move occurs because `some_vec` has type `std::vec::Vec<&str>`, which does not implement the `Copy` trait

			`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`.