rust/tests/ui/codemap_tests/tab.rs

// ignore-tidy-tab

fn main() {
	bar; //~ ERROR cannot find value `bar`
}

fn foo() {
	"bar			boo" //~ ERROR mismatched types
}
Add fix for tabs. Move error unit tests->ui tests 2016-07-13 21:53:42 +00:00			`// ignore-tidy-tab`
RUST_NEW_ERROR_FORMAT is no more 2016-08-16 07:52:30 +00:00
Add fix for tabs. Move error unit tests->ui tests 2016-07-13 21:53:42 +00:00			`fn main() {`
Merge cfail and ui tests into ui tests 2017-11-20 12:13:27 +00:00			bar; //~ ERROR cannot find value `bar`
Add fix for tabs. Move error unit tests->ui tests 2016-07-13 21:53:42 +00: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 06:47:13 +00:00
			`fn foo() {`
Merge cfail and ui tests into ui tests 2017-11-20 12:13:27 +00:00			`"bar boo" //~ ERROR mismatched types`
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 06:47:13 +00:00			`}`