Nathan Ridge

It's not entirely clear to me what your question is. Documentation for using clangd can be found here: https://clangd.llvm.org/installation#editor-plugins

Please share [clangd logs](https://clangd.llvm.org/troubleshooting.html#gathering-logs) for further diagnosis.

Likely duplicate of #1452

I added myself as a reviewer, but it will take me a while to get to, as I'm on travels right now, and I'm not really familiar with these Github...

@tamird could you elaborate on the motivation for this patch? Is there a problem you're experiencing as a vscode-clangd user (or developer) that this patch solves for you?

> @HighCommander4 sorry, neglected to reply. The motivation is that it's easier to stay current incrementally rather than having to do big-bang bumps like #664. My thoughts here are similar...

@tamird I'm finding dependabot to be making the commit history pretty noisy. 18 of the last 22 commits are from dependabot, over the course of ~1.5 months. That's a lot...

This diagnostic is coming from a [clang-tidy checker](https://clang.llvm.org/extra/clang-tidy/checks/bugprone/sizeof-expression.html). Please report issues with it upstream to clang-tidy at https://github.com/llvm/llvm-project/issues/. Clangd is just passing the clang-tidy diagnostics through.

Can you share [clangd logs](https://clangd.llvm.org/troubleshooting.html#gathering-logs)?

This looks like a client log. Can you share a server log, and one that covers the entire period from clangd startup until seeing the affected diagnostic?