87110e7d71
As this project grows, it might be beneficial to require pull requests to keep a certain level of test coverage. Plus it's a fun statistic. |
||
---|---|---|
src | ||
tests | ||
.gitignore | ||
.travis.yml | ||
Cargo.lock | ||
Cargo.toml | ||
Contributing.md | ||
Design.md | ||
README.md |
rustfmt
A tool for formatting Rust code according to style guidelines.
If you'd like to help out (and you should, it's a fun project!), see Contributing.md.
Installation
Note: this method currently requires you to be running cargo 0.6.0 or newer.
cargo install --git https://github.com/rust-lang-nursery/rustfmt
or if you're using multirust
multirust run nightly cargo install --git https://github.com/rust-lang-nursery/rustfmt
Running Rustfmt from Vim
See instructions.
How to build and test
First make sure you've got Rust 1.4.0 or greater available, then:
cargo build
to build.
cargo test
to run all tests.
cargo run -- filename
to run on a file, if the file includes out of line
modules, then we reformat those too. So to run on a whole module or crate, you
just need to run on the top file.
You'll probably want to specify the write mode. Currently, there are the
replace, overwrite, display and coverage modes. The replace mode is the default
and overwrites the original files after renaming them. In overwrite mode,
rustfmt does not backup the source files. To print the output to stdout, use the
display mode. The write mode can be set by passing the --write-mode
flag on
the command line.
cargo run -- filename --write-mode=display
prints the output of rustfmt to the
screen, for example.
What style does Rustfmt use?
Rustfmt is designed to be very configurable. You can create a TOML file called
rustfmt.toml, place it in the project directory and it will apply the options
in that file. See cargo run --help-config
for the options which are available,
or if you prefer to see source code, [src/config.rs].
By default, Rustfmt uses a style which (mostly) confirms to the Rust style guidelines. There are many details which the style guidelines do not cover, and in these cases we try to adhere to a style similar to that used in the Rust repo. Once Rustfmt is more complete, and able to re-format large repositories like Rust, we intend to go through the Rust RFC process to nail down the default style in detail.
If there are styling choices you don't agree with, we are usually happy to add options covering different styles. File an issue, or even better, submit a PR.
Gotchas
- For things you do not want rustfmt to mangle, use one of
#[rustfmt_skip] #[cfg_attr(rustfmt, rustfmt_skip)]
- When you run rustfmt, place a file named rustfmt.toml in target file directory or its parents to override the default settings of rustfmt.
- After successful compilation, a
rustfmt
executable can be found in the target directory.