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

Production lint category #5755

Open
Kestrer opened this issue Jun 27, 2020 · 0 comments
Open

Production lint category #5755

Kestrer opened this issue Jun 27, 2020 · 0 comments
Labels
A-category Area: Categorization of lints C-enhancement Category: Enhancement of lints, like adding more cases or adding help messages S-needs-discussion Status: Needs further discussion before merging or work can be started

Comments

@Kestrer
Copy link
Contributor

Kestrer commented Jun 27, 2020

About

This lint category collects all production code related lints, currently only including todo, unimplemented, dbg_macro, print_stdout and use_debug. This allows people to easily check whether they should release their code without having to remember the names of multiple lints and have to add and remove them, and allows Clippy to add more similar lints and have them be automatically enabled for all Rust production builds. Having these lints being in the restriction category doesn't really make sense because they are very useful for all Rust projects, just not all the time.

Drawbacks

It is a whole new lint category for just a couple lints.

@flip1995 flip1995 added S-needs-discussion Status: Needs further discussion before merging or work can be started C-enhancement Category: Enhancement of lints, like adding more cases or adding help messages labels Jun 28, 2020
@camsteffen camsteffen added the A-category Area: Categorization of lints label Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-category Area: Categorization of lints C-enhancement Category: Enhancement of lints, like adding more cases or adding help messages S-needs-discussion Status: Needs further discussion before merging or work can be started
Projects
None yet
Development

No branches or pull requests

3 participants