Nathan Ridge

See also #2342 for a special case (filtering by arity) that's easier to implement than the example given above.

One thing that's annoying here is that, in addition to (obviously) not being able to use high-level clangd functionality like `locateSymbolAt()`, tests meant to be upstreamable also don't get to...

> tests meant to be upstreamable also don't get to use things like `SelectionTree` It looks like **AST matchers** are a suitable upstream replacement for `SelectionTree` for the purpose of...

Proposed fix: https://github.com/llvm/llvm-project/pull/121313

A couple of thoughts / questions: 1. Does having a multi-root workspace need to imply using a separate clangd instance for each root? I can see use cases where this...

I have not been able to reproduce the crash so far based on your description. Can you please share the full contents of all relevant source files at the time...

So you never actually **invoke** the macro `Test_Flags_`, you only define it? I still can't reproduce the OOM on the code from your last comment. Can you share [clangd logs](https://clangd.llvm.org/troubleshooting.html#gathering-logs)...

In your logs, I see: > I[10:54:09.855] Enqueueing 590 commands for indexing suggesting that you have other source files in the project, and they are getting indexed by the background...

Is there something I could do to help move this effort forward? Having `clang-tools-extra` binaries such as `clang-tidy` and `clangd` in the archives would be super helpful for tracking down...

> Actually, it would be useful to know how far back you need. If you're happy with it just appearing in current/future packs then I can investigate turning it on...