Use Cargo's "namespace features" feature #4293
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cargo recently added the ability to have an optional dependency without
implicitly introducing a new named feature on a crate. This is triggered
with some new directives in the
[features]
section, specifically:The
dep:foo
syntax means thatfoo
is activated but no implicitfeature should be added named
foo
.Additionally
foo?/bar
means that thebar
feature offoo
is onlyactivated if
foo
is otherwise activated elsewhere, for example aconditional activation.
These two features can help avoid extra feature names showing up that we
don't want (e.g. currently the
wasmtime
crate has arayon
feature)and additionally can help avoid runtime dependencies in niche cases for
us (e.g. activating
all-arch
but disablingcranelift
wouldpreviously pull-in cranelift but no longer will).