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

Turn style lints to warn by default #11432

Closed
brson opened this issue Jan 10, 2014 · 3 comments · Fixed by #12290
Closed

Turn style lints to warn by default #11432

brson opened this issue Jan 10, 2014 · 3 comments · Fixed by #12290
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@brson
Copy link
Contributor

brson commented Jan 10, 2014

Our stylistic lints are set to allow currently, which makes them very ineffective at promoting a consistent style across the Rust ecosystem. We should turn them on and force users to opt out of the community style.

bors added a commit that referenced this issue Jan 21, 2014
The parens in `if (true) {}` are not necessary, so we'll warn about them.

cc #3070 and #11432
@lambda-fairy
Copy link
Contributor

Looks like #11457 has fixed the issue. Should we close this?

@huonw
Copy link
Member

huonw commented Feb 1, 2014

#11457 hasn't landed yet.

@mrshu
Copy link
Contributor

mrshu commented Feb 22, 2014

I was trying to set NonUppercaseStatics to warn and fix errors that might occur but I found out that many things depend on each other, like io/mod or io/process. What do you think should the right approach be? Just putting #[allow] there?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants