TL;DR: if you use any of
--no-default-features flags in your build, could you check that on the latest nightly, if you add
-Z package-features flag as well, everything continues to work?
Hi! We’ve recently noticed a rather surprising interaction of Cargo
--package flags. For command like
cargo build --package foo --feature feat, the feature would be activated not for the
foo package, but for the package at current working directory. Moreover, features of current package were always activated, so
cargo build --package foo might have activated more features than strictly necessary for building
foo! We would like to make this behavior more intuitive, and always apply features to the explicitly selected package. This is a change in behavior, so, for now, it is hidden behind an opt-in
-Z package-features flag. We would like to access the real-world impact of this change, so please try building your projects with this opt-in!