The output of the program is treated as a Rustc diagnostic message

[kkshinkai]

rust-analyzer version: 0.3.1194-standalone (67920f7 2022-09-04)

rustc version: rustc 1.61.0 (fe5b13d68 2022-05-18)

It seems that RA can't distinguish well between the output of Rust compiler and the output of the program. When I print a string similar to the Rust diagnostic message, VS Code reports it as a Rust error.

I found this problem because I was writing a diagnostic engine similar to Rustc's, and these red lines kept appearing in my test files.

To reproduce this issue in VSCode, you need to use the run button on the main function.

[bjorn3]

This is probably because the problem matcher used to show rustc errors in the editor window doesn't know how to distinguish compiler output from program output.

[kkshinkai]

I didn't find a way to tell VS Code how to match correctly. I'm not very familiar with VS Code extensions, but I think there's not much more we can do here.

rust-analyzer/editors/code/package.json

Lines 1180 to 1197 in b7e8b9a

	"problemPatterns": [
	{
	"name": "rustc",
	"patterns": [
	{
	"regexp": "^(warning|warn|error)(?:\\[(.*?)\\])?: (.*)$",
	"severity": 1,
	"code": 2,
	"message": 3
	},
	{
	"regexp": "^[\\s->=]*(.*?):(\\d*):(\\d*)\\s*$",
	"file": 1,
	"line": 2,
	"column": 3
	}
	]
	},

Maybe I should change my program to avoid ambiguity.