rust/tests/ui/codemap_tests/tab.stderr

error[E0425]: cannot find value `bar` in this scope
  --> $DIR/tab.rs:4:2
   |
LL |     bar;
   |     ^^^ not found in this scope

error[E0308]: mismatched types
  --> $DIR/tab.rs:8:2
   |
LL | fn foo() {
   |         - help: try adding a return type: `-> &'static str`
LL |     "bar            boo"
   |     ^^^^^^^^^^^^^^^^^^^^ expected `()`, found `&str`

error: aborting due to 2 previous errors

Some errors have detailed explanations: E0308, E0425.
For more information about an error, try `rustc --explain E0308`.
resolve: Do not use "resolve"/"resolution" in error messages 2017-01-12 01:18:08 +03:00			error[E0425]: cannot find value `bar` in this scope
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/tab.rs:4:2`
Add fix for tabs. Move error unit tests->ui tests 2016-07-13 17:53:42 -04:00			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| bar;`
Display `\t` in diagnostics code as four spaces 2017-11-12 22:06:00 -08:00			`\| ^^^ not found in this scope`
Add fix for tabs. Move error unit tests->ui tests 2016-07-13 17:53:42 -04: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 08:47:13 +02:00			`error[E0308]: mismatched types`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/tab.rs:8:2`
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 08:47:13 +02:00			`\|`
Update UI tests 2018-02-23 03:42:32 +03:00			`LL \| fn foo() {`
Point to where missing return type should go 2023-09-30 19:29:41 +00:00			\| - help: try adding a return type: `-> &'static str`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| "bar boo"`
Surround types with backticks in type errors 2019-11-15 09:37:01 -08:00			\| ^^^^^^^^^^^^^^^^^^^^ expected `()`, found `&str`
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 08:47:13 +02:00
			`error: aborting due to 2 previous errors`
Add fix for tabs. Move error unit tests->ui tests 2016-07-13 17:53:42 -04:00
hide `--explain` hint if error has no extended info 2019-04-17 13:26:38 -04:00			`Some errors have detailed explanations: E0308, E0425.`
update tests 2018-03-03 15:59:40 +01:00			For more information about an error, try `rustc --explain E0308`.