AaronBallman wrote:
> > > > 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
fmayer wrote:
> > > 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 `
AaronBallman wrote:
> > 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` ar
fmayer wrote:
> 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`?
https://github.com/llvm/llvm-project/pull/139594
___
cfe-commits mailing list
c
https://github.com/AaronBallman commented:
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 documenta
llvmbot wrote:
@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/ASTMa
https://github.com/fmayer created
https://github.com/llvm/llvm-project/pull/139594
This is useful for matching functions whose name is given as a
parameter, e.g.
Rate limit ยท GitHub
body {
background-color: #f6f8fa;
color: #24292e;
