Skip to content

Implement setting all lints to a given level #7185

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

Closed
wants to merge 1 commit into from
Closed

Implement setting all lints to a given level #7185

wants to merge 1 commit into from

Conversation

emberian
Copy link
Member

No description provided.

@alexcrichton
Copy link
Member

I'd be hesitant to include this. We have some different lints than with something like gcc's -Wall which I don't think actually turns on all the warnings. The major use case here I think would be -A all, whereas -D all and -W all would almost never be used.

I think that globally resetting all warnings would accomplish this same purpose, along with not introducing behavior which is almost never used.

Additionally here, as a lint attribute one would expect #[allow(all)] to work, but it doesn't work as implemented.

@alexcrichton
Copy link
Member

I think this can be closed now that #7371 is merged, the syntax would be -A warnings or -D warnings.

@emberian
Copy link
Member Author

Yup, thanks @alexcrichton

@emberian emberian closed this Jun 25, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request May 20, 2021
Fix duplicated "Rust 1.52" version section header

The most recent changelog update 037ddf2 accompanying the 1.52 release added a second "Rust 1.52" section header, with the result that the Rust release announcement https://blog.rust-lang.org/2021/05/06/Rust-1.52.0.html is linking to the "current beta" changelog section for Clippy rather than the stable changelog. I don't know the release process but based on previous changes to this file, I assume the correct thing to do is to mark the topmost section as being for Rust 1.53, not 1.52.

changelog: none
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants