diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2019-06-27 09:01:23 +0100 |
|---|---|---|
| committer | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2019-06-27 09:01:23 +0100 |
| commit | e8dc92ca734e34b25291015008d5c6dfd933fa7a (patch) | |
| tree | 399527ebfd1c7c36027aef8f03c337e6c160512a /crates/ra_tools/tests | |
| parent | b13a217a8b975d037b50c1b0e15073eabba582f8 (diff) | |
| parent | a8a1bc4b15b75e5702cb1ce1d4c5ab3153dbe3c9 (diff) | |
Merge #1450
1450: Extract lint scopes from `cargo watch` r=matklad a=etaoins
Currently all of our VS Code diagnostics are given the source of `rustc`. However, if you have something like `cargo-watch.command` set to `clippy` it will also watch for Clippy lints. The `rustc` source is a bit misleading in that case.
Fortunately, Rust's tool lints ([RFC 2103](https://github.com/rust-lang/rfcs/blob/master/text/2103-tool-attributes.md)) line up perfectly with VS Code's concept of `source`. This checks for lints scoped to a given tool and then splits them in to a `source` and tool-specific `code`.
Co-authored-by: Ryan Cumming <[email protected]>
Diffstat (limited to 'crates/ra_tools/tests')
0 files changed, 0 insertions, 0 deletions