2018-07-05 18:37:50 +08:00
# Clippy
2016-05-06 22:07:47 +08:00
2018-11-22 11:40:09 +08:00
[![Build Status ](https://travis-ci.org/rust-lang/rust-clippy.svg?branch=master )](https://travis-ci.org/rust-lang/rust-clippy)
2018-03-30 06:12:19 +08:00
[![Windows Build status ](https://ci.appveyor.com/api/projects/status/id677xpw1dguo7iw?svg=true )](https://ci.appveyor.com/project/rust-lang-libs/rust-clippy)
2018-05-04 20:23:53 +08:00
[![Current Version ](https://meritbadge.herokuapp.com/clippy )](https://crates.io/crates/clippy)
2018-10-06 03:37:50 +08:00
[![License: MIT/Apache-2.0 ](https://img.shields.io/crates/l/clippy.svg )](#license)
2014-11-19 15:50:46 +08:00
2017-10-15 03:47:38 +08:00
A collection of lints to catch common mistakes and improve your [Rust ](https://github.com/rust-lang/rust ) code.
2014-11-20 03:19:03 +08:00
2018-12-14 01:14:01 +08:00
[There are 291 lints included in this crate! ](https://rust-lang.github.io/rust-clippy/master/index.html )
2017-09-02 02:29:36 +08:00
2018-07-05 18:37:50 +08:00
We have a bunch of lint categories to allow you to choose how much Clippy is supposed to ~~annoy~~ help you:
2018-03-29 19:04:52 +08:00
2018-07-28 23:35:24 +08:00
* `clippy::all` (everything that has no false positives)
* `clippy::pedantic` (everything)
* `clippy::nursery` (new lints that aren't quite ready yet)
* `clippy::style` (code that should be written in a more idiomatic way)
* `clippy::complexity` (code that does something simple but in a complex way)
* `clippy::perf` (code that can be written in a faster way)
* `clippy::cargo` (checks against the cargo manifest)
* **`clippy::correctness`** (code that is just outright wrong or very very useless)
2018-03-29 19:04:52 +08:00
2018-11-22 11:40:09 +08:00
More to come, please [file an issue ](https://github.com/rust-lang/rust-clippy/issues ) if you have ideas!
2017-09-02 02:29:36 +08:00
2018-10-12 18:15:20 +08:00
Only the following of those categories are enabled by default:
* `clippy::style`
* `clippy::correctness`
* `clippy::complexity`
* `clippy::perf`
Other categories need to be enabled in order for their lints to be executed.
2016-02-22 22:50:40 +08:00
Table of contents:
2016-03-11 04:42:24 +08:00
2016-05-06 22:07:47 +08:00
* [Usage instructions ](#usage )
* [Configuration ](#configuration )
* [License ](#license )
2016-09-15 23:19:30 +08:00
## Usage
2016-11-19 11:46:12 +08:00
Since this is a tool for helping the developer of a library or application
2018-07-05 18:37:50 +08:00
write better code, it is recommended not to include Clippy as a hard dependency.
2016-11-20 11:16:36 +08:00
Options include using it as an optional dependency, as a cargo subcommand, or
2018-07-17 04:05:02 +08:00
as an included feature during build. These options are detailed below.
2016-11-19 11:46:12 +08:00
2018-07-17 04:05:02 +08:00
### As a cargo subcommand (`cargo clippy`)
2016-09-15 23:19:30 +08:00
2018-07-17 04:05:02 +08:00
One way to use Clippy is by installing Clippy through rustup as a cargo
subcommand.
2018-04-02 17:13:02 +08:00
2018-07-17 04:05:02 +08:00
#### Step 1: Install rustup
2018-04-02 17:13:02 +08:00
2018-07-17 04:05:02 +08:00
You can install [rustup ](http://rustup.rs/ ) on supported platforms. This will help
2018-09-12 02:29:00 +08:00
us install Clippy and its dependencies.
2017-12-28 00:06:40 +08:00
2018-07-17 04:05:02 +08:00
If you already have rustup installed, update to ensure you have the latest
rustup and compiler:
2017-12-28 00:06:40 +08:00
```terminal
2018-07-17 04:05:02 +08:00
rustup update
2017-12-28 00:06:40 +08:00
```
2018-09-12 02:29:00 +08:00
#### Step 2: Install Clippy
2018-01-12 18:33:13 +08:00
2018-09-12 02:29:00 +08:00
Once you have rustup and the latest stable release (at least Rust 1.29) installed, run the following command:
2018-04-02 17:13:02 +08:00
```terminal
2018-12-07 00:11:50 +08:00
rustup component add clippy
2018-04-02 17:13:02 +08:00
```
2018-09-12 02:29:00 +08:00
Now you can run Clippy by invoking `cargo clippy` .
2018-07-17 04:05:02 +08:00
2018-09-23 05:35:11 +08:00
If it says that it can't find the `clippy` subcommand, please run `rustup self update`
2018-07-05 18:37:50 +08:00
### Running Clippy from the command line without installing it
2016-09-15 23:19:30 +08:00
2018-07-05 18:37:50 +08:00
To have cargo compile your crate with Clippy without Clippy installation
2016-09-15 23:19:30 +08:00
in your code, you can use:
```terminal
2018-02-08 19:37:56 +08:00
cargo run --bin cargo-clippy --manifest-path=path_to_clippys_Cargo.toml
2016-09-15 23:19:30 +08:00
```
2018-11-22 11:40:09 +08:00
*[Note](https://github.com/rust-lang/rust-clippy/wiki#a-word-of-warning):*
2018-07-05 18:37:50 +08:00
Be sure that Clippy was compiled with the same version of rustc that cargo invokes here!
2016-09-15 23:19:30 +08:00
2018-09-14 14:21:14 +08:00
### Travis CI
You can add Clippy to Travis CI in the same way you use it locally:
```yml
2018-09-25 21:40:17 +08:00
language: rust
rust:
- stable
- beta
before_script:
2018-12-07 00:11:50 +08:00
- rustup component add clippy
2018-09-25 21:40:17 +08:00
script:
- cargo clippy
# if you want the build job to fail when encountering warnings, use
- cargo clippy -- -D warnings
# in order to also check tests and none-default crate features, use
- cargo clippy --all-targets --all-features -- -D warnings
- cargo test
# etc.
2018-09-14 14:21:14 +08:00
```
2018-12-11 05:30:16 +08:00
It might happen that Clippy is not available for a certain nightly release.
In this case you can try to conditionally install Clippy from the git repo.
2018-11-05 07:12:42 +08:00
```yaml
language: rust
rust:
- nightly
before_script:
2018-12-07 00:11:50 +08:00
- rustup component add clippy --toolchain=nightly || cargo install --git https://github.com/rust-lang/rust-clippy/ --force clippy
2018-11-05 07:12:42 +08:00
# etc
```
2016-09-15 23:19:30 +08:00
## Configuration
2018-09-02 17:31:39 +08:00
Some lints can be configured in a TOML file named `clippy.toml` or `.clippy.toml` . It contains a basic `variable = value` mapping eg.
2016-09-15 23:19:30 +08:00
```toml
blacklisted-names = ["toto", "tata", "titi"]
cyclomatic-complexity-threshold = 30
```
2018-11-22 11:50:00 +08:00
See the [list of lints ](https://rust-lang.github.io/rust-clippy/master/index.html ) for more information about which lints can be configured and the
2016-09-15 23:19:30 +08:00
meaning of the variables.
2018-01-07 19:50:42 +08:00
To deactivate the “for further information visit *lint-link* ” message you can
2017-09-01 16:29:49 +08:00
define the `CLIPPY_DISABLE_DOCS_LINKS` environment variable.
2016-09-15 23:19:30 +08:00
### Allowing/denying lints
2018-09-13 17:27:01 +08:00
You can add options to your code to `allow` /`warn`/`deny` Clippy lints:
2016-09-15 23:19:30 +08:00
2018-07-28 23:35:24 +08:00
* the whole set of `Warn` lints using the `clippy` lint group (`#![deny(clippy::all)]`)
2016-09-15 23:19:30 +08:00
2018-07-28 23:35:24 +08:00
* all lints using both the `clippy` and `clippy::pedantic` lint groups (`#![deny(clippy::all)]`,
`#![deny(clippy::pedantic)]` ). Note that `clippy::pedantic` contains some very aggressive
2016-09-15 23:19:30 +08:00
lints prone to false positives.
2018-07-28 23:35:24 +08:00
* only some lints (`#![deny(clippy::single_match, clippy::box_vec)]`, etc)
2016-09-15 23:19:30 +08:00
* `allow` /`warn`/`deny` can be limited to a single function or module using `#[allow(...)]` , etc
Note: `deny` produces errors instead of warnings.
2018-12-11 05:30:16 +08:00
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`
2018-10-02 16:39:51 +08:00
2018-12-21 15:11:06 +08:00
## [Contributing](https://github.com/rust-lang/rust-clippy/blob/master/CONTRIBUTING.md)
2016-05-06 22:07:47 +08:00
## License
2018-10-07 10:29:01 +08:00
Copyright 2014-2018 The Rust Project Developers
Licensed under the Apache License, Version 2.0 < LICENSE-APACHE or
http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
< LICENSE-MIT or http: / / opensource . org / licenses / MIT > , at your
option. All files in the project carrying such notice may not be
copied, modified, or distributed except according to those terms.