2019-12-22 21:43:54 +00:00
|
|
|
# Run rustfmt with this config (it should be picked up automatically).
|
2019-05-03 18:35:21 +00:00
|
|
|
version = "Two"
|
|
|
|
|
use_small_heuristics = "Max"
|
2019-12-22 21:43:54 +00:00
|
|
|
merge_derives = false
|
2019-10-29 15:33:11 +00:00
|
|
|
|
|
|
|
|
# by default we ignore everything in the repository
|
|
|
|
|
# tidy only checks files which are not ignored, each entry follows gitignore style
|
|
|
|
|
ignore = [
|
2020-01-31 16:09:34 +00:00
|
|
|
"build",
|
2020-02-11 03:08:24 +00:00
|
|
|
"/vendor/",
|
2020-01-31 16:09:34 +00:00
|
|
|
|
2019-12-22 21:43:54 +00:00
|
|
|
# tests for now are not formatted, as they are sometimes pretty-printing constrained
|
|
|
|
|
# (and generally rustfmt can move around comments in UI-testing incompatible ways)
|
|
|
|
|
"src/test",
|
|
|
|
|
|
2019-10-29 15:33:11 +00:00
|
|
|
# do not format submodules
|
|
|
|
|
"src/doc/book",
|
|
|
|
|
"src/doc/edition-guide",
|
|
|
|
|
"src/doc/embedded-book",
|
|
|
|
|
"src/doc/nomicon",
|
|
|
|
|
"src/doc/reference",
|
|
|
|
|
"src/doc/rust-by-example",
|
2020-03-10 20:22:25 +00:00
|
|
|
"src/doc/rustc-dev-guide",
|
2019-10-29 15:33:11 +00:00
|
|
|
"src/llvm-project",
|
|
|
|
|
"src/stdarch",
|
|
|
|
|
"src/tools/cargo",
|
|
|
|
|
"src/tools/clippy",
|
|
|
|
|
"src/tools/miri",
|
|
|
|
|
"src/tools/rls",
|
Add rust-analyzer submodule
The current plan is that submodule tracks the `release` branch of
rust-analyzer, which is updated once a week.
rust-analyzer is a workspace (with a virtual manifest), the actual
binary is provide by `crates/rust-analyzer` package.
Note that we intentionally don't add rust-analyzer to `Kind::Test`,
for two reasons.
*First*, at the moment rust-analyzer's test suite does a couple of
things which might not work in the context of rust repository. For
example, it shells out directly to `rustup` and `rustfmt`. So, making
this work requires non-trivial efforts.
*Second*, it seems unlikely that running tests in rust-lang/rust repo
would provide any additional guarantees. rust-analyzer builds with
stable and does not depend on the specifics of the compiler, so
changes to compiler can't break ra, unless they break stability
guarantee. Additionally, rust-analyzer itself is gated on bors, so we
are pretty confident that test suite passes.
2020-06-04 11:11:15 +00:00
|
|
|
"src/tools/rust-analyzer",
|
2019-10-29 15:33:11 +00:00
|
|
|
"src/tools/rust-installer",
|
|
|
|
|
"src/tools/rustfmt",
|
2019-12-24 21:21:26 +00:00
|
|
|
|
|
|
|
|
# We do not format this file as it is externally sourced and auto-generated.
|
|
|
|
|
"src/libstd/sys/cloudabi/abi/cloudabi.rs",
|
2019-10-29 15:33:11 +00:00
|
|
|
]
|
