cargo-hack
cargo-hack copied to clipboard
taiki-e
Cargo subcommand to provide various options useful for testing and continuous integration.
Notably, `cfg(debug_assertions)` can be used to enable/disable code paths, and it might also be useful to test on profiles both with overflow-checks on and off.
rust-lang/cargo#4866 has been closed, but the README still mentions it. Should the README be updated?
usecases: - https://github.com/rust-lang/regex/blob/d6bc7a4c3b58e1d618024aaededa722df32fa6e8/src/lib.rs#L613 - https://github.com/rust-lang/futures-rs/blob/3601bb76708ea4bcc14c3491237abc33b685ba0b/futures/src/lib.rs#L100 - https://doc.rust-lang.org/cargo/reference/features.html#mutually-exclusive-features
...any of v2 resolver, --no-dev-deps, -Zavoid-dev-deps, and -Zfeatures, and there are dev-deps. They are most likely not working properly. See also: https://github.com/tokio-rs/tokio/issues/4357#issuecomment-1002806945
Some context first: we are building a blockchain on [substrate](https://github.com/paritytech/substrate), and have a monorepo with a bunch of crates. Some crates are intended to be built in both std and...
--each-feature and --feature-powerset are great! My only complaint is that they are slow. bpytop shows that I'm never using more than one core when running cargo-hack. It would be awesome...
Hi, cargo-hack is awesome, thank you for making it! I'm running my CI pipeline using the `rust:latest` image, which always has the most recent point release installed: ``` root@a4a809c38181:/# rustup...
I don't really understand what `--group-features` is doing just from the readme or help output so it's possible I'm using it wrong and that this is possible already. I want...
The cargo-hack CLI is quite stable, so I think we can release 1.0. TODO: Investigate existing issues and TODOs.
The current readme just lists the options and it is not very easy to read. It may be good to add a section like "Examples" to introduce some commonly used...