On 31/03/17 19:43, Simon Sapin wrote:
# cargo check
Remember how I said a crate needs its dependencies to be compiled before
it can start compiling? It actually only needs metadata (the results of
the analysis phase), not the generated code.
Cargo added a `cargo check` command that skips code generation entirely
(except for build scripts and build-dependencies). This saves a lot of
time (I’ve measured up to 5× speed from `./mach clean`), though
obviously you don’t get an executable at the end. Still, it can help for
example during a refactoring: run `./mach cargo check` many times until
compiler error are resolved, and only then run `./mach build` and/or
`./mach test-unit`.
https://github.com/rust-lang/cargo/pull/3296
https://github.com/servo/servo/pull/14594
With a couple pull requests that just landed, "./mach cargo-geckolib
check" now also works. On a fast desktop it runs in 28 seconds after
"cargo clean" and 19 seconds after "touch components/style/lib.rs".
--
Simon Sapin
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
