about summary refs log tree commit diff
path: root/tests/incremental/thinlto
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2023-10-04 12:01:04 +0000
committerbors <bors@rust-lang.org>2023-10-04 12:01:04 +0000
commitad73597448a4d703dc7161c3f4a8a0602b1a12a0 (patch)
tree9b0fba1a9ed00de91e21c25c2a6020cfdf03fa5b /tests/incremental/thinlto
parent7e9da4007878fb0104812039c9835329306e15fa (diff)
parentdd8ea977b700d9ef6089dea6e5f1353f567c06d1 (diff)
downloadrust-ad73597448a4d703dc7161c3f4a8a0602b1a12a0.tar.gz
rust-ad73597448a4d703dc7161c3f4a8a0602b1a12a0.zip
Auto merge of #15690 - Enselic:fix-regexp, r=Veykril
vscode: Fix line and col regexp for `rustc` problem matcher

When building the Rust compiler with `./x check` from within VS Code, the current `rustc` problem matcher thinks that the output from that command that looks like this:

    Build completed successfully in 0:00:26

is about a problem in a file named `0` on line 00, col 26. This wouldn't be so bad if it wasn't for that VS Code tends to get stuck on this problem because of problems with opening the file '0'.

The rust compiler will never output problems with a line or a column that starts with 0, so change the regexp to require lines and cols to begin with `[1-9]` to fix this problem.
Diffstat (limited to 'tests/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions