[clang-tools-extra] [clang-tidy] Allow type-generic builtins in pro-type-vararg check (PR #178656)
via cfe-commits
cfe-commits at lists.llvm.org
Sat Jan 31 05:37:01 PST 2026
github-actions[bot] wrote:
<!--LLVM CODE FORMAT COMMENT: {clang-format}-->
:warning: C/C++ code formatter, clang-format found issues in your code. :warning:
<details>
<summary>
You can test this locally with the following command:
</summary>
``````````bash
git-clang-format --diff origin/main HEAD --extensions cpp -- clang-tools-extra/clang-tidy/cppcoreguidelines/ProTypeVarargCheck.cpp clang-tools-extra/test/clang-tidy/checkers/cppcoreguidelines/pro-type-vararg.cpp --diff_from_common_commit
``````````
:warning:
The reproduction instructions above might return results for more than one PR
in a stack if you are using a stacked PR workflow. You can limit the results by
changing `origin/main` to the base branch/commit you want to compare against.
:warning:
</details>
<details>
<summary>
View the diff from clang-format here.
</summary>
``````````diff
diff --git a/clang-tools-extra/clang-tidy/cppcoreguidelines/ProTypeVarargCheck.cpp b/clang-tools-extra/clang-tidy/cppcoreguidelines/ProTypeVarargCheck.cpp
index ac1be20f9..7c4286d41 100644
--- a/clang-tools-extra/clang-tidy/cppcoreguidelines/ProTypeVarargCheck.cpp
+++ b/clang-tools-extra/clang-tidy/cppcoreguidelines/ProTypeVarargCheck.cpp
@@ -183,7 +183,8 @@ void ProTypeVarargCheck::check(const MatchFinder::MatchResult &Result) {
// implementation detail to accept multiple types, not for C-style varargs.
if (const auto *FD = Matched->getDirectCallee())
if (const unsigned BuiltinID = FD->getBuiltinID();
- BuiltinID && Result.Context->BuiltinInfo.hasCustomTypechecking(BuiltinID))
+ BuiltinID &&
+ Result.Context->BuiltinInfo.hasCustomTypechecking(BuiltinID))
return;
diag(Matched->getExprLoc(), "do not call c-style vararg functions");
``````````
</details>
https://github.com/llvm/llvm-project/pull/178656
More information about the cfe-commits
mailing list