From b8ace1418cbbc260edf902bb617d1d535df4e12b Mon Sep 17 00:00:00 2001 From: firewave Date: Fri, 5 Jan 2024 13:39:23 +0100 Subject: [PATCH] updated clang-tidy.md --- clang-tidy.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/clang-tidy.md b/clang-tidy.md index 336e7365bf9..f54363c9342 100644 --- a/clang-tidy.md +++ b/clang-tidy.md @@ -35,7 +35,6 @@ These are coding guidelines we do not follow. Some of the checks might be explic `readability-isolate-declaration`
`modernize-use-trailing-return-type`
`readability-uppercase-literal-suffix`
-`readability-else-after-return`
`readability-identifier-length`
These do not reflect the style we are (currently) enforcing. @@ -72,7 +71,7 @@ This leads to a mismatch of raw string literals and regular ones and does reduce `-clang-analyzer-*`
-Disabled because of false positives (needs to file an upstream bug report). +Disabled because of false positives (need to file upstream bug reports). The checks are also quite time consuming. `misc-non-private-member-variables-in-classes`
@@ -82,7 +81,6 @@ We intentionally use this. Leads to lots of "false positives". This seem to enforce a coding guidelines of certain codebases. - `bugprone-easily-swappable-parameters`
This produces a lot of noise and they are not fixable that easily. @@ -121,7 +119,6 @@ We run this separately via `clang-include-cleaner` in the `iwyu.yml` workflow as `misc-throw-by-value-catch-by-reference`
`readability-avoid-const-params-in-decls`
`bugprone-signed-char-misuse`
-`readability-redundant-access-specifiers`
`concurrency-mt-unsafe`
`misc-use-anonymous-namespace`
`performance-avoid-endl`
@@ -186,7 +183,7 @@ We are not using SIMD instructions and it suggests to use `std::experiemental::` It does not seem to produce any warnings for us (needs to be investigated) and it is one of the more expensive checks. -`misc-unused-using-decls` +`misc-unused-using-decls`
This is the most expensive check for several files and it is providing much in terms of code quality. Reported upstream as https://github.com/llvm/llvm-project/issues/72300.