================ @@ -0,0 +1,48 @@ +//===--- TemplateVirtualMemberFunctionCheck.cpp - clang-tidy --------------===// +// +// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions. +// See https://llvm.org/LICENSE.txt for license information. +// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception +// +//===----------------------------------------------------------------------===// + +#include "TemplateVirtualMemberFunctionCheck.h" +#include "clang/ASTMatchers/ASTMatchFinder.h" + +using namespace clang::ast_matchers; + +namespace clang::tidy::portability { + +void TemplateVirtualMemberFunctionCheck::registerMatchers(MatchFinder *Finder) { + Finder->addMatcher(classTemplateSpecializationDecl().bind("specialization"), + this); +} + +void TemplateVirtualMemberFunctionCheck::check( + const MatchFinder::MatchResult &Result) { + const auto *MatchedDecl = + Result.Nodes.getNodeAs<ClassTemplateSpecializationDecl>("specialization"); + + if (MatchedDecl->isExplicitSpecialization()) + return; ---------------- 5chmidti wrote:
Nit: this `isExplicitSpecialization` could be moved into the matcher to avoid generating a match result: `unless(isExplicitTemplateSpecialization())` --- Technically, the whole `check` function can be moved to the matcher, as well. Let's see what others think. IIRC the general stance was to prefer the matchers, unless there are performance or readability/simplicity concerns. Though I don't really see the need to move the stuff below into the matcher. https://github.com/llvm/llvm-project/pull/110099 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
