2
2
3
3
This is a temporary notice.
4
4
5
- From May 9th, 2025 until the 1st of August, 2025 we will perform a feature freeze. Only bugfix PRs will be reviewed
6
- with the exception of already open ones. Every feature-adding PR opened in between those dates will be moved into a
5
+ From the 26th of June until the 18th of September we will perform a feature freeze. Only bugfix PRs will be reviewed
6
+ except already open ones. Every feature-adding PR opened in between those dates will be moved into a
7
7
milestone to be reviewed separately at another time.
8
8
9
9
We do this because of the long backlog of bugs that need to be addressed
10
- in order to contiue being the state of the art linter that Clippy has become known for being.
10
+ in order to continue being the state-of- the- art linter that Clippy has become known for being.
11
11
12
12
## For contributors
13
13
14
14
If you are a contributor or are planning to become one, ** please do not open a lint-adding PR** , we have lots of open
15
15
bugs of all levels of difficulty that you can address instead!
16
16
17
17
We currently have about 800 lints, each one posing a maintainability challenge that needs to account to every possible
18
- usecase of the whole ecosystem. Bugs are natural in every software, but the Clippy team considers that Clippy needs a
18
+ use case of the whole ecosystem. Bugs are natural in every software, but the Clippy team considers that Clippy needs a
19
19
refinement period.
20
20
21
21
If you open a PR at this time, we will not review it but push it into a milestone until the refinement period ends,
@@ -33,14 +33,14 @@ debugging, sometimes interacting directly with the upstream compiler. Difficult
33
33
improves a lot developer workflows!
34
34
35
35
- 🟧 [ Suggestion causes bug] [ sugg_causes_bug ] , Clippy suggested code that changed logic in some silent way.
36
- Unacceptable, as this may have disastreous consequences. Easier to fix than ICEs
36
+ Unacceptable, as this may have disastrous consequences. Easier to fix than ICEs
37
37
38
38
- 🟨 [ Suggestion causes error] [ sugg_causes_error ] , Clippy suggested code snippet that caused a compiler error
39
39
when applied. We need to make sure that Clippy doesn't suggest using a variable twice at the same time or similar
40
40
easy-to-happen occurrences.
41
41
42
42
- 🟩 [ False positives] [ false_positive ] , a lint should not have fired, the easiest of them all, as this is "just"
43
- identifying the root of a the false positive and making an exception for those cases.
43
+ identifying the root of a false positive and making an exception for those cases.
44
44
45
45
Note that false negatives do not have priority unless the case is very clear, as they are a feature-request in a
46
46
trench coat.
0 commit comments