Cargo could raise a warning when user defines an optional dependency which is not part of any feature.
I've been confused for a while trying to figure out why building my single feature project with --all-features was working while building it with --features=my-feature was not. Turned out I forgot to include one optional dep with the feature. Such warning would have prevent me from doing such stupid mistake. :)
Cargo could raise a warning when user defines an optional dependency which is not part of any feature.
I've been confused for a while trying to figure out why building my single feature project with
--all-featureswas working while building it with--features=my-featurewas not. Turned out I forgot to include one optional dep with the feature. Such warning would have prevent me from doing such stupid mistake. :)