Nathan Ridge

Ok, I see, this logging is implemented entirely in the client. > It's arguably more readable that one-liners from clangd. Note that clangd will also pretty-print the protocol traffic if...

This has a similar challenge to https://github.com/clangd/clangd/issues/639: the user _might_ be declaring a variable of pointer/reference type, but they might be declaring a variable of value type as well, and...

> For C, you have to write `struct S s;` in order to use S, while C++ only needs `S s;`. I understand that, but I'm not sure how it's...

There's a known OOM that was fixed in clangd 19 (https://github.com/clangd/clangd/issues/1384), affecting specifically large `.h` files with many preprocessor branches (typically encountered in single-header libraries like `miniaudio.h`), and another OOM...

> Is there a way to opt-in for clangd 19? I don't see it available on Homebrew or on GitHub. Would I need to compile it from source? Binary packages...

Well I guess it's clear that you're not running into either of the OOM bugs mentioned earlier, since those have different symptoms (the memory usage keeps growing). It's also clear...

I'm guessing from the `ModuleCache` in the directory name and the `.pcm` file extension that these files are related to [Modules](https://clang.llvm.org/docs/Modules.html). I know clangd's support for Modules is a work...

Transferred to the server repo for greater visibility. Maybe some folks from Apple, or others familiar with Clang Modules, can chime in.

> Can I somehow disable this problematic behavior while having clangd work to some extent? I don't understand the mechanism of the problematic behaviour enough to have a suggestion besides...

I'm not familiar enough with modules to give you a specific answer, but I can describe two general approaches for configuring clangd differently from the build. **Approach 1** The first...