A power law appears to be at work here. I use VSCode, and it works very well for me.
- 90%: Seeing the read squigglies, I already know my mistake (e.g., "cannot borrow X as mutable").
- 9%: A brief glance at the error description is required. (I'm having trouble coming up with an example. It's probably some random instance of the 90% bucket that I just didn't consider, and seeing the message it's immediately obvious.)
- .9%: The full error message is integral to understanding and solving the issue (e.g., "X is not Send because it contains Y over here").
- .1%: I pull my hair out for an hour or more (e.g., "implementation of X is not general enough").