Skip to content
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

Passing --cap-lints to cargo itself #7530

Open
mrcnski opened this issue Oct 21, 2019 · 1 comment
Open

Passing --cap-lints to cargo itself #7530

mrcnski opened this issue Oct 21, 2019 · 1 comment
Labels
A-lints Area: rustc lint configuration C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` S-needs-team-input Status: Needs input from team on whether/how to proceed.

Comments

@mrcnski
Copy link

mrcnski commented Oct 21, 2019

Hi all, I just found out about capping lint levels and it seems like it could be a highly useful feature for developers working on code which has the deny(warnings) anti-pattern enabled. However, while rustc supports this flag, cargo does not appear to, and I am wondering whether this is intentional or just that no one's suggested it yet.

It would be groovy if the various cargo subcommands like build, run, test, doc, and so on supported this flag.

@mrcnski mrcnski added the C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` label Oct 21, 2019
@mrcnski
Copy link
Author

mrcnski commented Oct 22, 2019

Relevant discussion: #3591

@ehuss ehuss added the A-lints Area: rustc lint configuration label Nov 8, 2019
@epage epage added the S-needs-team-input Status: Needs input from team on whether/how to proceed. label Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-lints Area: rustc lint configuration C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` S-needs-team-input Status: Needs input from team on whether/how to proceed.
Projects
None yet
Development

No branches or pull requests

3 participants