[clang] Add hasAnyNameInVector matcher

[fmayer]

This is useful for matching functions whose name is given as a
parameter, e.g.

[llvmbot]

@llvm/pr-subscribers-clang

Author: Florian Mayer (fmayer)

Changes

This is useful for matching functions whose name is given as a
parameter, e.g.

---

Full diff: https://github.com/llvm/llvm-project/pull/139594.diff

1 Files Affected:

• (modified) clang/include/clang/ASTMatchers/ASTMatchers.h (+18)

diff --git a/clang/include/clang/ASTMatchers/ASTMatchers.h b/clang/include/clang/ASTMatchers/ASTMatchers.h
index e6b684b24b080..255f7d3487f9d 100644
--- a/clang/include/clang/ASTMatchers/ASTMatchers.h
+++ b/clang/include/clang/ASTMatchers/ASTMatchers.h
@@ -3144,6 +3144,24 @@ extern const internal::VariadicFunction<internal::Matcher<NamedDecl>, StringRef,
                                         internal::hasAnyNameFunc>
     hasAnyName;
 
+/// Matches NamedDecl nodes that have any of the names in vector.
+///
+/// This is useful for matching a list of names that are only known at runtime,
+/// e.g. through a command line argument.
+///
+/// \code
+///     hasAnyName({a, b, c})
+/// \endcode
+///  is equivalent to
+/// \code
+///     anyOf(hasName(a), hasName(b), hasName(c))
+/// \endcode
+inline internal::Matcher<NamedDecl>
+hasAnyNameInVector(std::vector<std::string> Names) {
+  return internal::Matcher<NamedDecl>(
+      new internal::HasNameMatcher(std::move(Names)));
+}
+
 /// Matches NamedDecl nodes whose fully qualified names contain
 /// a substring matched by the given RegExp.
 ///

[AaronBallman]

Are there any planned in-tree uses for this matcher? We don't typically add matchers without a need in tree due to the overhead of the matcher interfaces.

If there are in-tree uses planned, then some additional work is needed: regenerate the documentation (there's a script in the docs directory) and test coverage. I don't think Registry.cpp needs to be updated though as this cannot be used via the dynamic matchers, I believe.

[fmayer]

Are there any planned in-tree uses for this matcher?

I had a downstream use planned. Does this mean I will have to reimplement internal::HasNameMatcher?

[AaronBallman]

Are there any planned in-tree uses for this matcher?

I had a downstream use planned. Does this mean I will have to reimplement internal::HasNameMatcher?

Can you adapt the code to use hasAnyName() instead, as that can accept a variadic number of StringRef arguments stored in an ArrayRef?

[fmayer]

Are there any planned in-tree uses for this matcher?

I had a downstream use planned. Does this mean I will have to reimplement internal::HasNameMatcher?

Can you adapt the code to use hasAnyName() instead, as that can accept a variadic number of StringRef arguments stored in an ArrayRef?

The use is for a runtime list of names, so I don't think the variadic would work?