Option to disable red-underlining large blocks of code

[k-stanislawek]

Rust analyzer tends to fill the whole function or file with red, like this:

This is annoying, I tend to disable the plugin for a moment when that happens.

It happens when I'm in the middle of writing a new function, or refactoring a function, and the error is "wrong return type". Sometimes I satisfy it by providing a return statement first, even mocked one, but it doesn't work if I want multiple branches with different returns.

Another use-case is when opening/closing brackets don't match, and red color makes it more difficult to find what's wrong.

[lnicola]

Please post some code (a complete function, preferably) where this happens.

This is probably a rustc error. rustc sometimes outputs error spans that are too large, and there's not much we can do about it, e.g. rust-lang/rust#77968.

[0x8f701]

Is there a way to change vscode's highlight group? I removed this by doing:https://github.com/GopherJ/cfg/blob/master/coc/.vimrc#L313-L330 in vim, I only keep line number error signs

[PatchMixolydic]

Workaround: using todo!() in place of a returned value will quiet any "wrong return type" errors (since todo! panics, it "returns" !, which coerces to any type).

[lnicola]

loop {} also works in a pinch.

[jonas-schievink]

Not sure if the original report was about a rustc issue, but the new native mismatched-type diagnostic also has this issue.