diff options
| author | Heejin Ahn <aheejin@gmail.com> | 2019-05-23 11:57:05 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-05-23 11:57:05 -0700 |
| commit | b1ecf05b3303fda057dcd87e46e75cb779d97f7d (patch) | |
| tree | 656f18f075797ee4927a1d9d1d22d1b0e134c970 /.clang-tidy | |
| parent | 257a4c5ac940fe14bb85518a78fc9dba1c78b959 (diff) | |
| download | binaryen-b1ecf05b3303fda057dcd87e46e75cb779d97f7d.tar.gz binaryen-b1ecf05b3303fda057dcd87e46e75cb779d97f7d.tar.bz2 binaryen-b1ecf05b3303fda057dcd87e46e75cb779d97f7d.zip | |
Disable clang static analyzer in clang-tidy (#2136)
clang-tidy by default enables two groups of checks: clang-diagnostic-*
and clang-analyzer-*. Between the two, clang-analyzer is a static
analyzer, but it seems to often produces false warnings. For example,
when you write `object->someFunction()`, if it is not sure if object is
not a NULL, i.e., if there's no assert(object) before, it produces a
warning. This is sometimes annoying and inserting `assert` everywhere
does not seem to be very appealing. I also noticed LLVM and V8 also
disabled this analyzer.
`-*` disables all checks. Then I re-enabled clang-diagnostic and
readability-braces-around-statements.
Diffstat (limited to '.clang-tidy')
| -rw-r--r-- | .clang-tidy | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/.clang-tidy b/.clang-tidy index dbc7730e6..c8e78f1c0 100644 --- a/.clang-tidy +++ b/.clang-tidy @@ -1,4 +1,4 @@ -Checks: 'readability-braces-around-statements' +Checks: '-*,clang-diagnostic-*,readability-braces-around-statements' CheckOptions: - key: readability-identifier-naming.ClassCase value: CamelCase |