vbvictor wrote:
I'm -1 on this change:
- You can use `-quiet` if don't want to look at verbose output
- I found it useful when integrating tidy in CI: if small number or none checks
were enabled, it indicated that some configuration was wrong. Also, if there is
only one `.clang-tidy` config for whole project, it's good to see which exact
checks run.
--------------------------------
> not human readable at all
Could you elaborate on this? `-list-checks` option seems to me in
human-readable format, test run:
```
C:\Users\Victor\repos\llvm-project>python3
clang-tools-extra/clang-tidy/tool/run-clang-tidy.py -p build
clang-tools-extra/clang-tidy/
Enabled checks:
llvm-else-after-return
llvm-header-guard
llvm-include-order
llvm-namespace-comment
llvm-prefer-isa-or-dyn-cast-in-conditionals
llvm-prefer-register-over-unsigned
llvm-qualified-auto
llvm-twine-local
misc-confusable-identifiers
misc-coroutine-hostile-raii
misc-definitions-in-headers
misc-header-include-cycle
misc-misleading-bidirectional
misc-misleading-identifier
misc-misplaced-const
misc-new-delete-overloads
misc-non-copyable-objects
misc-redundant-expression
misc-static-assert
misc-throw-by-value-catch-by-reference
misc-unconventional-assign-operator
misc-uniqueptr-reset-release
misc-unused-alias-decls
misc-unused-using-decls
misc-use-internal-linkage
readability-identifier-naming
```
https://github.com/llvm/llvm-project/pull/185229
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
