-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
--all-targets
doesn't work and contradicts the documentation
#5134
Comments
The current architecture of |
infinity0
added a commit
to infinity0/cargo
that referenced
this issue
Mar 7, 2018
infinity0
added a commit
to infinity0/cargo
that referenced
this issue
Mar 7, 2018
This reverts commit d46db71.
Closing, invalid. |
infinity0
added a commit
to infinity0/cargo
that referenced
this issue
Mar 15, 2018
This reverts commit d46db71.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
These were originally added in #4400, the problem is it currently doesn't work, "all targets" is in effect no matter what and the flag is totally redundant. This is because
CompileFilter
has aDefault
enum which matches all targets (seeCompileFilter::matches
) and thisDefault
enum is used in most cases (seeCompileFilter::new
).I suggest updating
CompileFilter::matches
to match only lib/bin targets forCompileFilter::Default
and updating the documentation to match.Note that doing nothing is not an option, the documentation is currently incorrect and at the very least needs to be fixed so every instance above says "X all targets (default)" i.e. all the flags are redundant.
The text was updated successfully, but these errors were encountered: