-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Issues: rust-lang/rust-clippy
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Suggestion for new lint: Cognitive Complexity
C-an-interesting-project
Category: Interesting projects, that usually are more involved design/code wise.
C-enhancement
Category: Enhancement of lints, like adding more cases or adding help messages
E-hard
Call for participation: This a hard problem and requires more experience or effort to work on
L-complexity
Lint: Belongs in the complexity lint group
S-needs-discussion
Status: Needs further discussion before merging or work can be started
#3793
opened Feb 21, 2019 by
felix91gr
non_send_fields_in_send_ty seems to be misguided
C-bug
Category: Clippy is not doing the correct thing
I-false-positive
Issue: The lint was triggered on code it shouldn't have
#8045
opened Nov 30, 2021 by
tspiteri
[Tracking issue] Rearrange location of some of the existing lints
C-an-interesting-project
Category: Interesting projects, that usually are more involved design/code wise.
C-tracking-issue
Category: Tracking Issue
E-medium
Call for participation: Medium difficulty level problem and requires some initial experience.
#6680
opened Feb 5, 2021 by
magurotuna
5 of 8 tasks
New lint: Use Area: New lints
good-first-issue
These issues are a good way to get started with Clippy
L-style
Lint: Belongs in the style lint group
Into
/TryInto
in bounds as opposed to From
/TryFrom
A-lint
#4894
opened Dec 10, 2019 by
Kixunil
if_same_then_else Should not warn for These issues are a good way to get started with Clippy
I-false-positive
Issue: The lint was triggered on code it shouldn't have
S-needs-discussion
Status: Needs further discussion before merging or work can be started
else if
blocks.
good-first-issue
#3770
opened Feb 16, 2019 by
kevincox
Findings from running Clippy on Servo
C-an-interesting-project
Category: Interesting projects, that usually are more involved design/code wise.
#164
opened Aug 13, 2015 by
Manishearth
Warn about trait bounds on struct and enum type parameters
A-lint
Area: New lints
E-medium
Call for participation: Medium difficulty level problem and requires some initial experience.
L-unnecessary
Lint: Warn about unnecessary code
T-middle
Type: Probably requires verifiying types
#1689
opened Apr 22, 2017 by
dtolnay
git subtree crashes: can't sync rustc clippy changes into rust-lang/rust-clippy
A-infra
Area: CI issues and issues that require full access for GitHub/CI
#5565
opened May 4, 2020 by
matthiaskrgr
Feature request: flag for non-zero exit status if warnings are present
E-needs-test
Call for participation: writing tests
#1209
opened Sep 2, 2016 by
beefsack
[epic] Improve lint config discoverability
A-ui
Area: Clippy interface, usage and configuration
C-an-interesting-project
Category: Interesting projects, that usually are more involved design/code wise.
#9880
opened Nov 19, 2022 by
nyurik
New lint: potentially unwinding caller-supplied operators in Area: New lints
unsafe
code
A-lint
#9200
opened Jul 18, 2022 by
Kixunil
Politely mention that Area: New lints
good-first-issue
These issues are a good way to get started with Clippy
T-middle
Type: Probably requires verifiying types
Box<&T>
is almost the most useless type you can have
A-lint
#2394
opened Jan 23, 2018 by
oli-obk
[Book]: Add new section for collections of lints, that focus on the same problem
A-documentation
Area: Adding or improving documentation
#11808
opened Nov 14, 2023 by
tigerros
Suggest using Area: New lints
as_mut()
and as_ref()
instead of (*ptr.as_ptr()).field
in unsafe Rust.
A-lint
#11339
opened Aug 14, 2023 by
that-ambuj
False positive for Category: Clippy is not doing the correct thing
let_underscore_future
C-bug
#9932
opened Nov 23, 2022 by
agostbiro
Have a lint against usize-to-u64 casts (or, against *all* integer casts)
A-lint
Area: New lints
good-first-issue
These issues are a good way to get started with Clippy
#9231
opened Jul 23, 2022 by
RalfJung
New lint: dangerous use of vec.set_len()
A-lint
Area: New lints
E-medium
Call for participation: Medium difficulty level problem and requires some initial experience.
L-correctness
Lint: Belongs in the correctness lint group
#4483
opened Sep 1, 2019 by
Shnatsel
Lint Area: New lints
good-first-issue
These issues are a good way to get started with Clippy
L-style
Lint: Belongs in the style lint group
T-middle
Type: Probably requires verifiying types
set_*
and get_*
methods that do nothing but access the field
A-lint
#1673
opened Apr 12, 2017 by
oli-obk
Passing mutable references
A-lint
Area: New lints
E-medium
Call for participation: Medium difficulty level problem and requires some initial experience.
L-unnecessary
Lint: Warn about unnecessary code
T-MIR
Type: This lint will require working with the MIR
#353
opened Sep 28, 2015 by
Pyriphlegethon
Better testing of clippy lints before enabling them by default
C-an-interesting-project
Category: Interesting projects, that usually are more involved design/code wise.
#6429
opened Dec 7, 2020 by
dvc94ch
False positive for inherent_to_string_shadow_display?
C-bug
Category: Clippy is not doing the correct thing
C-enhancement
Category: Enhancement of lints, like adding more cases or adding help messages
good-first-issue
These issues are a good way to get started with Clippy
I-false-positive
Issue: The lint was triggered on code it shouldn't have
L-suggestion
Lint: Improving, adding or fixing lint suggestions
#4396
opened Aug 16, 2019 by
huxi
lint: transmuting known null pointer to ref
A-lint
Area: New lints
good-first-issue
These issues are a good way to get started with Clippy
T-AST
Type: Requires working with the AST
#628
opened Feb 6, 2016 by
llogiq
Add option to disable all linting in external macros
S-needs-discussion
Status: Needs further discussion before merging or work can be started
T-macros
Type: Issues with macros and macro expansion
#407
opened Oct 22, 2015 by
jFransham
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.