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
Support allow non_upper_case_globals lint. #198
Comments
This is my only disappointment with bitflags; I know that technically the macro isn't generating an enum, but bit flags are frequently defined as enums in C/C++, and it's natural to prefer enum variant casing rules for the bitflags here. |
When creating ffi bindings to c/c++ libs it gets especially annoying, having to have your bitflag variant named ANY_MODIFIER as opposed to AnyModifier to get rid of those warning is really annoying... |
I'm trying to create a bitflags with CamelCase naming. However adding #[allow(non_upper_case_globals)] everywhere doesn't suppress the lints.
The text was updated successfully, but these errors were encountered: