rust/README.md

214 lines
6.8 KiB
Markdown
Raw Normal View History

2016-05-06 14:07:47 +00:00
# rust-clippy
[![Build Status](https://travis-ci.org/rust-lang-nursery/rust-clippy.svg?branch=master)](https://travis-ci.org/rust-lang-nursery/rust-clippy)
[![Windows build status](https://ci.appveyor.com/api/projects/status/github/rust-lang-nursery/rust-clippy?svg=true)](https://ci.appveyor.com/project/rust-lang-nursery/rust-clippy)
2016-02-13 12:13:28 +00:00
[![Current Version](http://meritbadge.herokuapp.com/clippy)](https://crates.io/crates/clippy)
[![License: MPL-2.0](https://img.shields.io/crates/l/clippy.svg)](#license)
2014-11-19 07:50:46 +00:00
A collection of lints to catch common mistakes and improve your [Rust](https://github.com/rust-lang/rust) code.
2014-11-19 19:19:03 +00:00
2018-03-28 21:49:32 +00:00
[There are 248 lints included in this crate!](https://rust-lang-nursery.github.io/rust-clippy/master/index.html)
2018-03-29 11:04:52 +00:00
We have a bunch of lint categories to allow you to choose how much clippy is supposed to ~~annoy~~ help you:
* `clippy` (everything that has no false positives)
* `clippy_pedantic` (everything)
* `clippy_style` (code that should be written in a more idiomatic way)
* `complexity` (code that does something simple but in a complex way)
* `perf` (code that can be written in a faster way)
* **`correctness`** (code that is just outright wrong or very very useless)
More to come, please [file an issue](https://github.com/rust-lang-nursery/rust-clippy/issues) if you have ideas!
2016-02-22 14:50:40 +00:00
Table of contents:
2016-03-10 20:42:24 +00:00
2016-05-06 14:07:47 +00:00
* [Usage instructions](#usage)
* [Configuration](#configuration)
* [License](#license)
2016-09-15 15:19:30 +00:00
## Usage
Since this is a tool for helping the developer of a library or application
write better code, it is recommended not to include clippy as a hard dependency.
Options include using it as an optional dependency, as a cargo subcommand, or
as an included feature during build. All of these options are detailed below.
2016-09-15 15:19:30 +00:00
As a general rule clippy will only work with the *latest* Rust nightly for now.
### As a cargo subcommand (`cargo clippy`)
One way to use clippy is by installing clippy through cargo as a cargo
subcommand.
```terminal
2018-01-12 10:33:13 +00:00
cargo +nightly install clippy
```
2018-01-12 10:33:13 +00:00
(The `+nightly` is not necessary if your default `rustup` install is nightly)
Now you can run clippy by invoking `cargo +nightly clippy`.
In case you are not using rustup, you need to set the environment flag
`SYSROOT` during installation so clippy knows where to find `librustc` and
similar crates.
```terminal
SYSROOT=/path/to/rustc/sysroot cargo install clippy
```
2016-09-15 15:19:30 +00:00
### Optional dependency
2016-09-15 15:19:30 +00:00
In some cases you might want to include clippy in your project directly, as an
optional dependency. To do this, just modify `Cargo.toml`:
2016-09-15 15:19:30 +00:00
```toml
[dependencies]
clippy = { version = "*", optional = true }
```
2016-09-15 15:19:30 +00:00
And, in your `main.rs` or `lib.rs`, add these lines:
2016-09-15 15:19:30 +00:00
```rust
#![cfg_attr(feature="clippy", feature(plugin))]
#![cfg_attr(feature="clippy", plugin(clippy))]
2016-09-15 15:19:30 +00:00
```
Then build by enabling the feature: `cargo +nightly build --features "clippy"`.
2016-09-15 15:19:30 +00:00
Instead of adding the `cfg_attr` attributes you can also run clippy on demand:
`cargo rustc --features clippy -- -Z no-trans -Z extra-plugins=clippy`
2017-03-17 07:30:29 +00:00
(the `-Z no trans`, while not necessary, will stop the compilation process after
typechecking (and lints) have completed, which can significantly reduce the runtime).
2016-09-15 15:19:30 +00:00
Alternatively, to only run clippy when testing:
2016-09-15 15:19:30 +00:00
```toml
2018-01-01 21:55:40 +00:00
[dev-dependencies]
clippy = { version = "*" }
2016-09-15 15:19:30 +00:00
```
and add to `main.rs` or `lib.rs`:
2016-09-15 15:19:30 +00:00
```
#![cfg_attr(test, feature(plugin))]
#![cfg_attr(test, plugin(clippy))]
2016-09-15 15:19:30 +00:00
```
### Running clippy from the command line without installing it
2016-09-15 15:19:30 +00:00
To have cargo compile your crate with clippy without clippy installation and without needing `#![plugin(clippy)]`
2016-09-15 15:19:30 +00:00
in your code, you can use:
```terminal
cargo run --bin cargo-clippy --manifest-path=path_to_clippys_Cargo.toml
2016-09-15 15:19:30 +00:00
```
*[Note](https://github.com/rust-lang-nursery/rust-clippy/wiki#a-word-of-warning):*
2016-09-15 15:19:30 +00:00
Be sure that clippy was compiled with the same version of rustc that cargo invokes here!
### As a Compiler Plugin
*Note:* This is not a recommended installation method.
2016-09-15 15:19:30 +00:00
Since stable Rust is backwards compatible, you should be able to
compile your stable programs with nightly Rust with clippy plugged in to
circumvent this.
Add in your `Cargo.toml`:
```toml
[dependencies]
clippy = "*"
```
You then need to add `#![feature(plugin)]` and `#![plugin(clippy)]` to the top
of your crate entry point (`main.rs` or `lib.rs`).
Sample `main.rs`:
```rust
#![feature(plugin)]
#![plugin(clippy)]
fn main(){
let x = Some(1u8);
match x {
Some(y) => println!("{:?}", y),
_ => ()
}
}
```
Produces this warning:
```terminal
src/main.rs:8:5: 11:6 warning: you seem to be trying to use match for destructuring a single type. Consider using `if let`, #[warn(single_match)] on by default
src/main.rs:8 match x {
src/main.rs:9 Some(y) => println!("{:?}", y),
src/main.rs:10 _ => ()
src/main.rs:11 }
src/main.rs:8:5: 11:6 help: Try
if let Some(y) = x { println!("{:?}", y) }
```
## Configuration
Some lints can be configured in a TOML file named with `clippy.toml` or `.clippy.toml`. It contains basic `variable = value` mapping eg.
2016-09-15 15:19:30 +00:00
```toml
blacklisted-names = ["toto", "tata", "titi"]
cyclomatic-complexity-threshold = 30
```
See the [list of lints](https://rust-lang-nursery.github.io/rust-clippy/master/index.html) for more information about which lints can be configured and the
2016-09-15 15:19:30 +00:00
meaning of the variables.
You can also specify the path to the configuration file with:
```rust
#![plugin(clippy(conf_file="path/to/clippy's/configuration"))]
```
To deactivate the “for further information visit *lint-link*” message you can
2017-09-01 08:29:49 +00:00
define the `CLIPPY_DISABLE_DOCS_LINKS` environment variable.
2016-09-15 15:19:30 +00:00
### Allowing/denying lints
You can add options to `allow`/`warn`/`deny`:
* the whole set of `Warn` lints using the `clippy` lint group (`#![deny(clippy)]`)
* all lints using both the `clippy` and `clippy_pedantic` lint groups (`#![deny(clippy)]`,
`#![deny(clippy_pedantic)]`). Note that `clippy_pedantic` contains some very aggressive
lints prone to false positives.
* only some lints (`#![deny(single_match, box_vec)]`, etc)
* `allow`/`warn`/`deny` can be limited to a single function or module using `#[allow(...)]`, etc
Note: `deny` produces errors instead of warnings.
For convenience, `cargo clippy` automatically defines a `cargo-clippy`
features. This lets you set lints level and compile with or without clippy
transparently:
```rust
#[cfg_attr(feature = "cargo-clippy", allow(needless_lifetimes))]
```
2017-10-11 18:50:58 +00:00
## Updating rustc
Sometimes, rustc moves forward without clippy catching up. Therefore updating
rustc may leave clippy a non-functional state until we fix the resulting
breakage.
You can use the [rust-update](rust-update) script to update rustc only if
clippy would also update correctly.
2016-05-06 14:07:47 +00:00
## License
Licensed under [MPL](https://www.mozilla.org/MPL/2.0/).
If you're having issues with the license, let me know and I'll try to change it to something more permissive.