diff options
author | Aleksey Kladov <[email protected]> | 2021-05-23 21:31:59 +0100 |
---|---|---|
committer | Aleksey Kladov <[email protected]> | 2021-05-25 15:49:59 +0100 |
commit | 5c9f31d4c28478b4373e6cf5ec155745c840ee3f (patch) | |
tree | 6d105121d271c7532170875feafaadcd7ad500ba /crates/syntax/test_data/parser/fragments/path/ok | |
parent | b7414fa14a85f4acd37b5bdfdc2a4ab97a072bd2 (diff) |
internal: move diagnostics to hir
The idea here is to eventually get rid of `dyn Diagnostic` and
`DiagnosticSink` infrastructure altogether, and just have a `enum
hir::Diagnostic` instead.
The problem with `dyn Diagnostic` is that it is defined in the lowest
level of the stack (hir_expand), but is used by the highest level (ide).
As a first step, we free hir_expand and hir_def from `dyn Diagnostic`
and kick the can up to `hir_ty`, as an intermediate state. The plan is
then to move DiagnosticSink similarly to the hir crate, and, as final
third step, remove its usage from the ide.
One currently unsolved problem is testing. You can notice that the test
which checks precise diagnostic ranges, unresolved_import_in_use_tree,
was moved to the ide layer. Logically, only IDE should have the infra to
render a specific range.
At the same time, the range is determined with the data produced in
hir_def and hir crates, so this layering is rather unfortunate. Working
on hir_def shouldn't require compiling `ide` for testing.
Diffstat (limited to 'crates/syntax/test_data/parser/fragments/path/ok')
0 files changed, 0 insertions, 0 deletions