You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an optional, feature-activated dependency is also listed under dev-dependencies it will be pulled in by cargo build even without the feature being requested:
Development dependencies are traversed during the resolution process, causing
them to be returned as the list of dependencies for a package in terms of
resolution. The compilation phase would then filter these out depending on the
dependency's transitivity, but this was incorrectly accounted for when the
dependency showed up multiple times in a few lists.
This commit fixes this behavior by updating the filtering logic to ensure that
only activated optional dependencies (those whose feature names are listed) are
compiled.
Closesrust-lang#1805
Development dependencies are traversed during the resolution process, causing
them to be returned as the list of dependencies for a package in terms of
resolution. The compilation phase would then filter these out depending on the
dependency's transitivity, but this was incorrectly accounted for when the
dependency showed up multiple times in a few lists.
This commit fixes this behavior by updating the filtering logic to ensure that
only activated optional dependencies (those whose feature names are listed) are
compiled.
Closes#1805
If an optional, feature-activated dependency is also listed under
dev-dependencies
it will be pulled in bycargo build
even without the feature being requested:Removing the
dev-dependencies
section builds the package as expected:Edit: cargo is at version 0.4.0-nightly (15b497b 2015-07-08) (built 2015-07-12)
The text was updated successfully, but these errors were encountered: