Coverage percentage is misleading, as 60% coverage has a different meaning for 800 LOC vs 80 KLOC. Perhaps uncovered line count is better?
Related Posts
It's rare to see ANSI escape codes for URLs in the wild, but cargo has it!
This example links to https://doc.rust-lang.org/cargo/reference/profiles.html#default-profiles, describing the different profiles.
Considering releases vs debug is a source of confusion for new users expecting better performance, this seems wise.
I'm experimenting with diagnostics formatting.
* I've added a left margin, showing both the file name and line numbers
* I'm showing one line of context above/below the offending line.
* I'm using grey for comments.
What do you think? Is there anything you'd change?
In LSP, a position is represented as a line number and a column offset (in Unicode code units): https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#position
This is pretty elegant. You'll get the correct line regardless of encoding bugs, and the editor already knows the line number so it's cheap to compute.