about summary refs log tree commit diff
path: root/src/test/debuginfo/enum-thinlto.rs
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2022-04-05 16:31:18 +0000
committerGitHub <noreply@github.com>2022-04-05 16:31:18 +0000
commitee6becc5dde3aff7bdb5ff5081d79d6351797563 (patch)
tree4a26f423c0e309a04f1b55d611b76f231edc4d03 /src/test/debuginfo/enum-thinlto.rs
parentb5eaf566669055b4dfb191b21117cff8125ada7f (diff)
parent84cf6ad09190cc72a5daf45181812f555162235c (diff)
downloadrust-ee6becc5dde3aff7bdb5ff5081d79d6351797563.tar.gz
rust-ee6becc5dde3aff7bdb5ff5081d79d6351797563.zip
Merge #11891
11891: Better error message on Flycheck Error message (from: unactionable error message if we are using `clippy` as the checker) r=Veykril a=flipbit03

I have commented on this [S-unactionable issue](https://github.com/rust-analyzer/rust-analyzer/issues/6589) that the Flycheck error message should maybe provide a hint about what tool it actually runs. Searching on some places on the Internet I've found multiple people, including myself, losing copious amounts of time on the same issue. So I've decided to make this very small PR :-)

From an user experience standpoint, the current error message is unhelpful to the end user, because the end user does not know exactly what it needs to check/fix (outdated, broken, or missing `cargo clippy`). In my own case, `cargo clippy` was actually missing altogether (developing off `rust:1.59.0-bullseye` official Docker image).

Thanks in advance!




Co-authored-by: Cadu <cadu.coelho@gmail.com>
Diffstat (limited to 'src/test/debuginfo/enum-thinlto.rs')
0 files changed, 0 insertions, 0 deletions