cargo-hack
cargo-hack copied to clipboard
taiki-e
Cargo subcommand to provide various options useful for testing and continuous integration.
--each-feature is a flag to check each feature. It may be all feature combinations that the user actually wanted to check. related: https://github.com/hyperium/hyper/pull/2422
related: #58, #47, https://github.com/rust-lang/futures-rs/pull/2277, https://github.com/hyperium/hyper/pull/2423, #227
Running cargo-hack on a workspace requesting a specific feature to be enabled will require the feature to be enabled on every crate, and will cause an error when a crate...
Is there a way for me to make `cargo-hack` keep the compiled binary after each run? I'm thinking of something like this: ```bash # Assume crate foo has features alpha...
UPDATE(taiki-e): - The situation here has been improved, and the latest cargo-hack overwrites the existing `Cargo.lock` only when it is necessary to work around old cargo bugs (https://github.com/taiki-e/cargo-hack/pull/242). If you...
## Description This is a feature-gated implementation of multi-threading for this project. This utilizes `rayon` for performing multi-threading. This PR is raised against #128. ## Reasoning Following are some of...
Would it make sense to adapt `cargo-hack` for checking dependency version resolution per crate in a workspace? Especially with `-Z minimal-versions`. If I have: * workspace * `my_crate1 ` *...
Packages can have two MSRVs - Local development / as a git dependency - As a registry dependency For example, if you use workspace inheritance, your local development / git...
https://github.com/taiki-e/cargo-hack/pull/175