Open Vtec234 opened 5 years ago
I would be interested in picking up this issue
@mcdermott111 You are very welcome to do that :)
What is the best way to decide which clang-tidy errors to be checking for. I think it would be unnecessary to have every single error turned on. The following are the set of errors I was thinking of including so far: clang-analyzer, bugprone, concurrency, performance and their respective sub-errors. Here is the list of all clang-tidy errors: https://clang.llvm.org/extra/clang-tidy/checks/list.html
@mcdermott111 I think these are good choices. We can always be more thorough later if we want.
clang-tidy
can detect lots of C++ programming and style errors, so it would be worthwile to have it included inmake check
. To do so, a Python module invoking it should be added tobuildsystem.codecompliance
.