`readability-identifier-naming` should add universal default options

[cjdb]

I almost always want my casing to be "lower_case", and it'd be nice to provide a default case, and only spell out the ones that don't conform to this (e.g. macros).

[llvmbot]

Hi!

This issue may be a good introductory issue for people new to working on LLVM. If you would like to work on this issue, your first steps are:

1. In the comments of the issue, request for it to be assigned to you.
2. Fix the issue locally.
3. Run the test suite locally. Remember that the subdirectories under test/ create fine-grained testing targets, so you can e.g. use make check-clang-ast to only run Clang's AST tests.
4. Create a Git commit.
5. Run git clang-format HEAD~1 to format your changes.
6. Open a pull request to the upstream repository on GitHub. Detailed instructions can be found in GitHub's documentation.

If you have any further questions about this issue, don't hesitate to ask via a comment in the thread below.

[llvmbot]

@llvm/issue-subscribers-clang-tidy

Author: Christopher Di Bella (cjdb)

I almost always want my casing to be "lower_case", and it'd be nice to provide a default case, and only spell out the ones that don't conform to this (e.g. macros).

[llvmbot]

@llvm/issue-subscribers-good-first-issue

Author: Christopher Di Bella (cjdb)

I almost always want my casing to be "lower_case", and it'd be nice to provide a default case, and only spell out the ones that don't conform to this (e.g. macros).

[kannishk]

Hey, @cjdb please assign me this issue. Would love to hack around!

[kannishk]

Hey @EugeneZelenko
I had a doubt.

Till now I have been trying to make this a part of the coding standard and errors should arise if anything deviates.(This doesn't seem to work)

I believe that clang-format should be one enforcing this change; Am I right on this part?
The developer can write the code and clang-format making it prettier later.

[kannishk]

Hey @EugeneZelenko I had a doubt.

Till now I have been trying to make this a part of the coding standard and errors should arise if anything deviates.(This doesn't seem to work)

I believe that clang-format should be one enforcing this change; Am I right on this part? The developer can write the code and clang-format making it prettier later.

@cjdb

[kannishk]

Hey @EugeneZelenko I had a doubt.

Till now I have been trying to make this a part of the coding standard and errors should arise if anything deviates.(This doesn't seem to work)

I believe that clang-format should be one enforcing this change; Am I right on this part? The developer can write the code and clang-format making it prettier later.

@EugeneZelenko @cjdb

[usx95]

I believe that clang-format should be one enforcing this change; Am I right on this part? The developer can write the code and clang-format making it prettier later.

This is not about formatting the code. clang-format only formats the code but does not enforce or change naming conventions.

This is done as part of the mentioned clangtidy check. You might find the following files helpful:
https://clang.llvm.org/extra/clang-tidy/checks/readability/identifier-naming.html
https://github.com/llvm/llvm-project/blob/main/clang-tools-extra/clang-tidy/readability/IdentifierNamingCheck.h
https://github.com/llvm/llvm-project/blob/main/clang-tools-extra/clang-tidy/readability/IdentifierNamingCheck.cpp

[kannishk]

Thanks @usx95 for clarifying!
No wonder it wasn't working