aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/CodeGen/CodeGenModule.h
diff options
context:
space:
mode:
authorSt. Muench <stmuench@gmx.net>2025-09-07 21:54:37 +0200
committerGitHub <noreply@github.com>2025-09-07 22:54:37 +0300
commit6fc32e93066c59a39b3c8c9be4e4f416653a917e (patch)
treeb0cd0217f6e37bb101f358ee431902a1c076bfb3 /clang/lib/CodeGen/CodeGenModule.h
parentac60477295ef6c3683dd862984a7fcedb1a352d9 (diff)
downloadllvm-6fc32e93066c59a39b3c8c9be4e4f416653a917e.zip
llvm-6fc32e93066c59a39b3c8c9be4e4f416653a917e.tar.gz
llvm-6fc32e93066c59a39b3c8c9be4e4f416653a917e.tar.bz2
[clang-tidy] do not diagnose array types within implicit instantiations of a template (#132924)
So far, the clang-tidy check `modernize-avoid-c-arrays` also diagnosed array types for type template parameters even though no actual array type got written there but it got deduced to one. In such case, there is nothing a developer can do at that location to fix the diagnostic. Since in this case, the location where the template got actually instantiated would have to be adjusted. And this is in most cases some totally distant code where implementers of a template do not have access to. Also adding suppressions to the declaration of the template is not an option since that would clutter the code unnecessarily and is in many cases also simply not possible (e.g. for users of a template). Hence, we propose to not diagnose any occurrence of an array type in an implicit instantiation of a template but rather at the point where template arguments involve array types.
Diffstat (limited to 'clang/lib/CodeGen/CodeGenModule.h')
0 files changed, 0 insertions, 0 deletions