readme: tool lints are stable now #3527
Conversation
|
Nit: perhaps throw in a quick note that this also works with lint groups? (like |
README.md
Outdated
| ``` | ||
|
|
||
| If you do not want to include your lint levels in your code, you can globally enable/disable lints by passing extra flags to clippy during the run: `cargo clippy -- -A lint_name` will run clippy with `lint_name` disabled and `cargo clippy -- -W lint_name` will run it with that enabled. On newer compilers you may need to use `clippy::lint_name` instead. | ||
| If you do not want to include your lint levels in your code, you can globally enable/disable lints by passing extra flags to clippy during the run: `cargo clippy -- -A clippy::lint_name` will run clippy with `lint_name` disabled and `cargo clippy -- -W clippy::lint_name` will run it with that enabled. This also works with lint groups. For example you can run Clippy with warnings for all lints enabled: `cargo clippy -- -W clippy::pedantic` |
There was a problem hiding this comment.
Ah, there was some convention to always use Clippy (capitalized) instead of clippy established some time ago I think?
r=me with that changed (sorry should have remembered earlier =/ )
There was a problem hiding this comment.
You're right =) I also changed it in some more places in 0c93e4c just now
There was a problem hiding this comment.
Now I see it still mentions nightly there.. I will fix that too while I'm at it.
README.md
Outdated
| rust: | ||
| - nightly | ||
| before_script: | ||
| - rustup component add clippy --toolchain=nightly || cargo install --git https://github.com/rust-lang/rust-clippy/ --force clippy |
There was a problem hiding this comment.
Hmm, I think this is still useful for people who want to run clippy on the nightly channel instead of beta or stable.
There was a problem hiding this comment.
As in, this hack was useful before it was broken (#3523) for people who didn't want to wait for new rust releases to get clippy updates.
There was a problem hiding this comment.
removed that commit again, should be fine now 👍
phansch
force-pushed
the
update_readme2
branch
from
c31543c to
0c93e4c
Compare
|
@bors r=matthiaskrgr |
|
📌 Commit 0c93e4c has been approved by |
readme: tool lints are stable now None
|
☀️ Test successful - status-appveyor, status-travis |
No description provided.