-
Notifications
You must be signed in to change notification settings - Fork 19
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
CamelCase for acronym typenames? #25
Comments
I have conflicted feelings about this. On one hand, it'd be nice to follow an official recommendation. OTOH that looks weird to me. In non-Rust languages it's |
I think same-language conventions have greater value for code readability than across-language conventions. As such I am in favor of this change. |
Also worth adding the |
Yeah, I'm not sure about this. It is possible to support both, by re-exporting the other with |
The principle of least surprise. Since you are split fairly evenly between the two options can I suggest we default to |
OK, that makes sense |
Rust's RFC 0430 about naming conventions says:
For consistency among other codes, I think
RGB
andRGBA
should beRgb
andRgba
.(
RGBA
looks like a constant rather than a type.)What do you think?
The text was updated successfully, but these errors were encountered: