Add .clang-tidy for better style and best practices linting #1680
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With a
.clang-tidy
, text editors and IDE's that have integration with clang-tidy (or clangd) will be able to complain about anti-patterns, and it can also help with enforcing code style in ways that clang-format can't. clang-tidy is basically a better clang-check.The file currently has what I think is probably a good starting point, which is turning all checks on and then turning off some of the checks that conflict with what has been done. The choice of checks to use is pretty subjective, so project leads may want to refer to https://clang.llvm.org/extra/clang-tidy/checks/list.html and choose which ones they will want to disable/enable.