Skip to content

Commit 3bd0305

Browse files
committed
clippy -> Clippy
1 parent d9b3276 commit 3bd0305

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

text/0000-clippy-uno.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -27,20 +27,20 @@ about its lints and their categorization.
2727

2828
## Usage and lint philosophy
2929

30-
We expect clippy to be used via `cargo clippy`.
30+
We expect Clippy to be used via `cargo clippy`.
3131

3232
Clippy aims to follow the general Rust style. It may be somewhat opiniated in some situations.
3333

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
3535
disagree with Clippy's choices. This is a weaker philosophy than that behind rustc's lints, where usually flipping
3636
one is an indication of a very specialized situation.
3737

3838
## Lint attributes
3939

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.
4141

4242
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.
4444

4545

4646
## Stability guarantees
@@ -108,7 +108,7 @@ discussion will bring up lints that the community feels _should_ be uplifted and
108108

109109
Such an uplift may change the lint level; correctness lints are Deny
110110
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).
112112

113113

114114
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).
660660

661661
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.
662662

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
664664
both reflect and affect the general style of the community.
665665

666666
# Unresolved questions

0 commit comments

Comments
 (0)