[MLIR][NFC] Ignore clang-tidy modernize-use-using check in C code - #180326
Conversation
|
@llvm/pr-subscribers-mlir Author: Twice (PragmaTwice) ChangesIn the MLIR C API headers, clang-tidy’s Full diff: https://github.com/llvm/llvm-project/pull/180326.diff 1 Files Affected:
diff --git a/mlir/.clang-tidy b/mlir/.clang-tidy
index eb8cbbeb9723c..0d4a4b1214837 100644
--- a/mlir/.clang-tidy
+++ b/mlir/.clang-tidy
@@ -58,3 +58,5 @@ CheckOptions:
value: camelBack
- key: readability-identifier-naming.VariableCase
value: camelBack
+ - key: modernize-use-using.IgnoreExternC
+ value: true
|
makslevental
left a comment
There was a problem hiding this comment.
interesting that this isn't automatically the case given that it can recognize extern "C"
|
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/169/builds/19764 Here is the relevant piece of the build log for the reference |
…lvm#180326) In the MLIR C API headers, clang-tidy’s `modernize-use-using` check reports a large number of type definitions that use `typedef`. In my IDE, this even causes the `typedef` code to be shown as struck through. However, in this case it is clearly not possible to replace them with `using`. This PR suppresses the `modernize-use-using` check for the code inside `extern "C"` blocks.
In the MLIR C API headers, clang-tidy’s
modernize-use-usingcheck reports a large number of type definitions that usetypedef. In my IDE, this even causes thetypedefcode to be shown as struck through. However, in this case it is clearly not possible to replace them withusing. This PR suppresses themodernize-use-usingcheck for the code insideextern "C"blocks.