Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

request: option to also enumerate second-order features #29

Closed
kentfredric opened this issue Mar 14, 2020 · 1 comment · Fixed by #70
Closed

request: option to also enumerate second-order features #29

kentfredric opened this issue Mar 14, 2020 · 1 comment · Fixed by #70
Labels
A-features Area: features (--feature-powerset, --each-feature, etc.) C-enhancement Category: A new feature or an improvement for an existing one

Comments

@kentfredric
Copy link

A little known thing is you can do:

 cargo test --features "foo/bar"

Which activates the "bar" feature of the "foo" crate. ( it makes sense when you see how features are defined in Cargo.toml ).

Subsequently, this means there is a way to expand test coverage to test situations where somebody turns on that feature in a different crate, and you get it through cargo composition.

So it would be nice if there was a way to test these, understandably, the set size it may generate could be prohibitively large in some cases, so its not a sensible default.

@taiki-e taiki-e added the C-enhancement Category: A new feature or an improvement for an existing one label Mar 19, 2020
@taiki-e taiki-e added the A-features Area: features (--feature-powerset, --each-feature, etc.) label Oct 10, 2020
@bors bors bot closed this as completed in 3fa63e8 Oct 19, 2020
@taiki-e
Copy link
Owner

taiki-e commented Oct 21, 2020

Added in 0.4.0 (#70).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-features Area: features (--feature-powerset, --each-feature, etc.) C-enhancement Category: A new feature or an improvement for an existing one
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants