mirror of
https://github.com/rust-lang/rust-analyzer
synced 2025-01-08 11:18:48 +00:00
6d6cb25cf4
Currently we depend on the ASCII rendering string that `rustc` provides
to populate Visual Studio Code's diagnostic. This has a number of
shortcomings:
1. It's not a very good use of space in the error list
2. We can't jump to secondary spans (e.g. where a called function is
defined)
3. We can't use Code Actions aka Quick Fix
This moves all of the low-level parsing and mapping to a
`rust_diagnostics.ts`. This uses some heuristics to map Rust diagnostics
to VsCode:
1. As before, the Rust diagnostic message and primary span is used for
the root diagnostic. However, we now just use the message instead of
the rendered version.
2. Every secondary span is converted to "related information". This
shows as child in the error list and can be jumped to.
3. Every child diagnostic is categorised in to three buckets:
1. If they have no span they're treated as another line of the root
messages
2. If they have replacement text they're treated as a Code Action
3. If they have a span but no replacement text they're treated as
related information (same as secondary spans).
|
||
|---|---|---|
| .. | ||
| analyzer_status.ts | ||
| apply_source_change.ts | ||
| cargo_watch.ts | ||
| index.ts | ||
| join_lines.ts | ||
| line_buffer.ts | ||
| matching_brace.ts | ||
| on_enter.ts | ||
| parent_module.ts | ||
| runnables.ts | ||
| syntaxTree.ts | ||
| watch_status.ts | ||