-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Allow using crate features that only exist in an override #2582
Comments
Yeah activating new features in path overrides currently isn't supported (intentionally) because the DAG needs to be resolved before path dependencies are loaded. I'm... a little surprised the In any case, the freshly-landed |
For example:
This is not allowed by cargo if
newfeature
doesn't exist upstream, even if there is an override that has the new crate feature flag.However, the feature flag can still be enabled manually
cargo build --features=num-complex/newfeature
.If this worked as expected (using Cargo.toml), it would make it easier to test the new feature using a whole chain / group of crates that depend on it.
The text was updated successfully, but these errors were encountered: