On 06/07/2017 03:18, Nathan Froyd wrote:
Cargo recently added a subcommand, `cargo check`, to perform type
checking of Rust crates without the additional step of code
generation. As code generation tends to dominate Rust compilation
times, `cargo check` speeds up the edit-borrow checker-bewilderment
cycle.
This command is now available for toplevel crates (gkrust,
gkrust-gtest, geckodriver, and mozjs_sys) via the `mach cargo check`
command. You can run:
$ mach cargo check
which checks gkrust (i.e. everything that goes into libxul). You can
check other crates:
$ mach cargo check gkrust-gtest
or even multiple crates:
$ mach cargo check gkrust gkrust-gtest
If you have ideas on how this command could be improved, please bugs
in Core :: Build Config.
Nice, thank you!
Would it make sense to allow arbitrary Cargo sub-commands? In Servo I
end up using `mach cargo update` for manipulating Cargo.lock, `mach
cargo rustc` for passing debugging options to the compiler, etc.
--
Simon Sapin
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
