-
Notifications
You must be signed in to change notification settings - Fork 424
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
Underscore nomenclature #16219
Comments
Hi @damon-kwok — Would you clarify what you are proposing we do here in order to address and close this issue? |
@bradcray If possible, add naming constraints to the chapel compiler. |
It's possible, but not something I think we would turn on by default. Personally, at least, I'm not a big fan of having languages impose naming constraints, as I think it's something a project's authors should decide for themselves given that different programmers prefer different styles (obviously). Where things get trickier is with the standard libraries where, as you've probably seen, we've been using camelCase fairly consistently, and I think it would be too difficult/painful for users if we were to change now. So I suspect that the best bet here would be to have the compiler support style flags like |
@bradcray Sound good! THANKS~ |
If you would like to open an issue specifically requesting such style-enforcement flags, please feel free to. |
Use underscore nomenclature to replace variable and method names with
littlecamel-case
nomenclature.The pony code on the right is more beautiful. See:
The text was updated successfully, but these errors were encountered: