-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
many_single_char_names incorrectly triggered if 'single-char-binding-names-threshold = 0' #4086
Labels
C-bug
Category: Clippy is not doing the correct thing
good-first-issue
These issues are a good way to get started with Clippy
Comments
oli-obk
added
A-musing
good-first-issue
These issues are a good way to get started with Clippy
labels
May 12, 2019
Hi, Could I take a look at this issue? |
@Toxyxer sure, go ahead =) |
Merged
Hey @phansch, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-bug
Category: Clippy is not doing the correct thing
good-first-issue
These issues are a good way to get started with Clippy
As I don't want to allow ANY variable names with only one character, I have the following
clippy.toml
:Additionally, I run clippy with
-- -D warnings
to force myself to write clean & idiomatic code.However, now clippy (and therefore all my CI jobs) fail with the following error:
This can also be reproduced by a simple hello-world example, as generated by running
cargo new
, as demonstrated here:I know that it worked a few months back but I cannot tell you when exactly it stopped working as I haven't programmed in a while..
If I set the value to
1
, then clippy does not complain, so I guess there's a wrong>=
instead of just>
somewhere..clippy version:
Edit/Note: I can't reproduce this if I clone
rust-clippy
and run clippy from this repository, so maybe/probably this was already fixed since the last release?The text was updated successfully, but these errors were encountered: