jade
99f159c536
This has not yet had all the warnings Obliterated, but it is a start and
is not *super* far away from being able to run the current configuration
in CI, which will catch some limited number of mistakes.
I tried the meson clang-tidy target and it seems to fail to find flags
for several files, which seems broken. Unsure what is up with that, but
we can use run-clang-tidy or other tooling instead.
We have an extremely annoying situation with the lexer table, which
means that the lexer probably must be moved to another directory with
its own .clang-tidy file to disable the lints in it, *or* write scuffed
code that prepends a disable comment to the top of the generated file.
None of the comment-based lint disabling features work since yacc dumps
a bunch of non compliant code at the top of the file before anything the
user can control.
Change-Id: I1d2aa6ec32deb1db1fbd581127334db1b972323c
19 lines
536 B
YAML
19 lines
536 B
YAML
UseColor: true
|
|
Checks:
|
|
- -*
|
|
- bugprone-*
|
|
# too many warnings
|
|
- -bugprone-assignment-in-if-condition
|
|
# too many warnings
|
|
- -bugprone-narrowing-conversions
|
|
# kind of nonsense
|
|
- -bugprone-easily-swappable-parameters
|
|
# too many warnings for now
|
|
- -bugprone-implicit-widening-of-multiplication-result
|
|
# Lix's exception handling is Questionable
|
|
- -bugprone-empty-catch
|
|
# many warnings
|
|
- -bugprone-unchecked-optional-access
|
|
# many warnings, seems like a questionable lint
|
|
- -bugprone-branch-clone
|