rust/src/test/ui/cross/cross-file-errors/main.stderr

error: expected expression, found reserved identifier `_`
  --> $DIR/underscore.rs:8:9
   |
LL |         _
   |         ^ expected expression
   | 
  ::: $DIR/main.rs:5:5
   |
LL |     underscore!();
   |     -------------- in this macro invocation
   |
   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error
syntax: Make `_` an identifier 2018-03-08 05:27:23 -06:00			error: expected expression, found reserved identifier `_`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/underscore.rs:8:9`
Add line numbers and columns to error messages spanning multiple files If an error message is emitted that spans several files, only the primary file currently has line and column data attached. This is useful information, even in files other than the one in which the error occurs. We can often work out which line and column the error corresponds to in other files — in this case it is helpful to add them (in the case of ambiguity, the first relevant line/column is picked, which is still helpful than none). 2018-01-26 09:33:05 -06:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| _`
Add label to primary span in some parse errors 2018-02-19 01:08:23 -06:00			`\| ^ expected expression`
Add line numbers and columns to error messages spanning multiple files If an error message is emitted that spans several files, only the primary file currently has line and column data attached. This is useful information, even in files other than the one in which the error occurs. We can often work out which line and column the error corresponds to in other files — in this case it is helpful to add them (in the case of ambiguity, the first relevant line/column is picked, which is still helpful than none). 2018-01-26 09:33:05 -06:00			`\|`
Remove licenses 2018-12-25 09:56:47 -06:00			`::: $DIR/main.rs:5:5`
Add line numbers and columns to error messages spanning multiple files If an error message is emitted that spans several files, only the primary file currently has line and column data attached. This is useful information, even in files other than the one in which the error occurs. We can often work out which line and column the error corresponds to in other files — in this case it is helpful to add them (in the case of ambiguity, the first relevant line/column is picked, which is still helpful than none). 2018-01-26 09:33:05 -06:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| underscore!();`
Add line numbers and columns to error messages spanning multiple files If an error message is emitted that spans several files, only the primary file currently has line and column data attached. This is useful information, even in files other than the one in which the error occurs. We can often work out which line and column the error corresponds to in other files — in this case it is helpful to add them (in the case of ambiguity, the first relevant line/column is picked, which is still helpful than none). 2018-01-26 09:33:05 -06:00			`\| -------------- in this macro invocation`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 07:56:47 -06:00			`\|`
			`= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)`
Add line numbers and columns to error messages spanning multiple files If an error message is emitted that spans several files, only the primary file currently has line and column data attached. This is useful information, even in files other than the one in which the error occurs. We can often work out which line and column the error corresponds to in other files — in this case it is helpful to add them (in the case of ambiguity, the first relevant line/column is picked, which is still helpful than none). 2018-01-26 09:33:05 -06:00
Update tests 2018-03-15 10:13:47 -05:00			`error: aborting due to previous error`