Aleksey Kladov efa069d288 internal: start new diagnostics API ... At the moment, this moves only a single diagnostic, but the idea is reafactor the rest to use the same pattern. We are going to have a single file per diagnostic. This file will define diagnostics code, rendering range and fixes, if any. It'll also have all of the tests. This is similar to how we deal with assists. After we refactor all diagnostics to follow this pattern, we'll probably move them to a new `ide_diagnostics` crate. Not that we intentionally want to test all diagnostics on this layer, despite the fact that they are generally emitted in the guts on the compiler. Diagnostics care to much about the end presentation details/fixes to be worth-while "unit" testing. So, we'll unit-test only the primary output of compilation process (types and name res tables), and will use integrated UI tests for diagnostics.		2021-06-13 14:55:45 +03:00
..
src	internal: start new diagnostics API	2021-06-13 14:55:45 +03:00
Cargo.toml	internal: cross-crate cov-marks	2021-06-12 23:40:52 +03:00