|0.0.149||Jan 16, 2023|
|0.0.145||Dec 26, 2022|
|0.0.141||Nov 28, 2022|
|0.0.122||Jul 25, 2022|
|0.0.66||Jul 26, 2021|
5,404 downloads per month
Used in 7 crates (via ra_ap_ide)
Diagnostics rendering and fixits.
Instead, we "bubble up" raw, structured diagnostics until the
where we "cook" them so that each diagnostic is formulated in terms of
types. Well, at least that's the aspiration, the "cooking" is somewhat
ad-hoc at the moment. Anyways, we get a bunch of ide-friendly diagnostic
structs from hir, and we want to render them to unified serializable
representation (span, level, message) here. If we can, we also provide
fixits. By the way, that's why we want to keep diagnostics structured
internally -- so that we have all the info to make fixes.
We have one "handler" module per diagnostic code. Such a module contains rendering, optional fixes and tests. It's OK if some low-level compiler functionality ends up being tested via a diagnostic.
There are also a couple of ad-hoc diagnostics implemented directly here, we don't yet have a great pattern for how to do them properly.