@@ -27,20 +27,20 @@ about its lints and their categorization.
27
27
28
28
## Usage and lint philosophy
29
29
30
- We expect clippy to be used via ` cargo clippy ` .
30
+ We expect Clippy to be used via ` cargo clippy ` .
31
31
32
32
Clippy aims to follow the general Rust style. It may be somewhat opiniated in some situations.
33
33
34
- In general clippy is intended to be used with a liberal sprinkling of ` #[allow()] ` and ` #[warn()] ` ; _ it is okay_ to
34
+ In general Clippy is intended to be used with a liberal sprinkling of ` #[allow()] ` and ` #[warn()] ` ; _ it is okay_ to
35
35
disagree with Clippy's choices. This is a weaker philosophy than that behind rustc's lints, where usually flipping
36
36
one is an indication of a very specialized situation.
37
37
38
38
## Lint attributes
39
39
40
- Currently to allow/deny clippy lints you have to ` #[cfg_attr(clippy, allow(lintname))] ` which is somewhat tedious.
40
+ Currently to allow/deny Clippy lints you have to ` #[cfg_attr(clippy, allow(lintname))] ` which is somewhat tedious.
41
41
42
42
The compiler should support something like ` #[allow(clippy::lintname)] ` which won't attempt to warn about nonexistant lints
43
- at all when not running clippy .
43
+ at all when not running Clippy .
44
44
45
45
46
46
## Stability guarantees
@@ -108,7 +108,7 @@ discussion will bring up lints that the community feels _should_ be uplifted and
108
108
109
109
Such an uplift may change the lint level; correctness lints are Deny
110
110
by default in Clippy but would probably switch to Warn if uplifted since the compiler is more
111
- conservative here (Using clippy is in itself an opt-in to a "please annoy me more" mode).
111
+ conservative here (Using Clippy is in itself an opt-in to a "please annoy me more" mode).
112
112
113
113
114
114
We'd also like to establish a rough policy for future lints here: Some correctness lints should probably belong in the compiler,
@@ -660,7 +660,7 @@ implement equality for a type involving floats).
660
660
661
661
We don't particularly _ need_ a 1.0, however it's good to have a milestone here, and a general idea of stability as we move forward in this process.
662
662
663
- It's also good to have some community involvement in the lint design/categorization process since clippy lints
663
+ It's also good to have some community involvement in the lint design/categorization process since Clippy lints
664
664
both reflect and affect the general style of the community.
665
665
666
666
# Unresolved questions
0 commit comments