no highliting when cmake compilation fails

[lukaz-vaultree-com]

Hi, my code was not highliting the errors and I took entire day to realize it was because the cmake C++ part of the code was failing to compile.

Maybe add this failure info at least on the output?

[Veykril]

So in a nutshell what is happening is that a dependency fails to build with an error, and we end up just eating that error without showing the user any such information right?

[lukaz-vaultree-com]

Yes. If the build.rs fails, then nothing is displayed and the error highlighting does not work, which made me unaware of what was happening

[Veykril]

So I just checked, if you have a dependency whose build script fails to build r-a does show you a warning status

[lukaz-vaultree-com]

@Veykril yes, I saw that but once I hovered my mouse it pops-up a giant message but for less than 0.1 second so I could not read it. Reading the rust-analyzer output on the VSCode outputs did not show an error

[jonas-schievink]

I've noticed that the popup can get so large that it appears under the cursor, which causes VS Code / Electron to immediately hide it again, which then makes it pop up again, using a lot of CPU, so I'm guessing we aren't meant to put that much text in it :)

I'm not really sure how to do better here – we could emit an actual diagnostic and put it in the workspace's Cargo.toml, or print it to stderr when the rust-analyzer logo is clicked, but neither seems ideal.

[bjorn3]

What about opening a new special page filled by rust-analyzer just like for example the memory stats? Also is it possible for the problems pane to refer to such special page? Or can it only refer to regular source files?