Skip to content

Make the naming lints only warn on names with upper/lowercase equivalents #21765

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

Merged
merged 1 commit into from
Jan 31, 2015

Conversation

ftxqxd
Copy link
Contributor

@ftxqxd ftxqxd commented Jan 30, 2015

An alternative to #21749.

This also refactors the naming lint code a little bit and slightly rephrases some warnings (uppercase → upper case).

Closes #21735.

@rust-highfive
Copy link
Contributor

r? @pnkfelix

(rust_highfive has picked a reviewer for you, use r? to override)

@pnkfelix
Copy link
Member

(is it just me, or is the logic in is_snake_case trickier to follow than one would usually expect? ... its probably just me; I kept reading the whole expression that sets allow_underscore as producing the returned value, but that is only in one branch of the match)

@pnkfelix
Copy link
Member

@bors: r+ 39a8c23

alexcrichton added a commit to alexcrichton/rust that referenced this pull request Jan 30, 2015
An alternative to rust-lang#21749.

This also refactors the naming lint code a little bit and slightly rephrases some warnings (`uppercase` → `upper case`).

Closes rust-lang#21735.
@alexcrichton alexcrichton merged commit 39a8c23 into rust-lang:master Jan 31, 2015
@tshepang
Copy link
Member

It's not just you @pnkfelix. It made me wonder if it could be made more easy to digest.

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.

Using unicode literals as indentifier produces a weird warning about snake case
5 participants