Repository navigation
Conversation
|
did you consider why these checks aren't enabled? |
Three findings from the checks the project's own .clang-tidy already globs in, limited to changes that cannot alter behaviour: - readability-uppercase-literal-suffix: `0u` -> `0U`. - readability-simplify-boolean-expr: distribute the negation over the disjunction in RunInThread() and in IsTruthyFlagValue(), rather than negating the whole expression. - misc-use-anonymous-namespace: the file-local console reporter helpers IgnoreColorPrint() and FormatTime() move into an anonymous namespace instead of being marked static. This deliberately leaves out misc-const-correctness, which accounts for most of what clang-tidy reports here and is the part that is purely a matter of taste. Happy to add or drop any of the above. No functional change. Release and debug builds are clean and the test suite passes.
ed9e8d9 to
ebf6a31
Compare
|
I read the question as: the config globs them in, but that is not the same as the project wanting them applied. So I have cut this down to the three findings that are not a matter of taste:
The |
|
so maybe we should start by running clang-tidy on CI (or even on pre-commit) before we add more fixes. fwiw, i wouldn't care about u vs U. the anonymous namespace fix is nice. |
|
Thanks for the feedback. It sounds like agreeing on clang tidy enforcement should come first, so I will close this PR for now. Once the project decides which checks to enforce, I can send focused cleanup patches that match that polic |
Works through part of the collated clang-tidy list, restricted to changes that cannot alter behaviour:
No functional change. Release and debug builds are clean and the test suite passes.
Per AGENTS.md: AI-assisted — the patch was drafted with AI assistance
(Claude) and then reviewed, tested, and understood by me. I take full
responsibility for it.