cargo-all-features
cargo-all-features copied to clipboard
frewsxcv
A Cargo subcommand to build and test all feature flag combinations.
### Current Config (as I understand it) - `skip_feature_sets`: A set of sets. Any feature set from the matrix that is a superset of any members will be dropped. -...
Most places use a feature list but refer to it as a set. (When I was refactoring, I kept the list behaviour and called it `FeatureList`.) However, the deny list...
I use [this tool](https://pre-commit.com/) in many of my projects to manage git hooks that run various lints. The yaml file is roughly my standard for rust projects and the shell...
Could there be a way to just print out the commands instead of executing them? For our continuous integration setup in Github, we're noticing that the wall clock times of...
The output of any given run is quite noisy. I propose only showing the output of failing runs and show a summary report instead. Perhaps showing the currently running set...
Suppose I have a workspace with crates `foo` and `bar`: ``` - Cargo.toml - foo | - Cargo.toml - bar | - Cargo.toml ``` If I want to run `cargo...
Hi. I was about to write this utility and then I found yours :) It would be nice to have `miri test` support. It would be exactly like `test-all-features` except...
My crate currently has 10 features, it will then explode to 2^10 = 1024 combinations. It'd be useful to be able to test some meaningful subsets of all the possible...
When used in the root of a workspace, the normal "cargo build" and "cargo test" commands (and similar) take the list of packages to build/test from the workspace.default-members key if...
Specifying `-p` in a workspace still enumerates featuers from packages not specified on command line
I have a workspace with different crates with their own features. If I specify `-p` to select one or more packages with `test-all-features` it appears all features from unspecified packages...
