Nathan Ridge

> > I do see that there is a code example in the PR description -- is that what consuming code would actually look like? For example, it would have...

In the interest of trying to move this forward, I'm going to add myself as a reviewer, and if we don't hear a strong objection from @sam-mccall, @kadircet, or @hokein,...

@thegecko I checked out this branch in order to play around with it; however, it's not building for me. After running `npm install` and then `npm run package`, I get:...

Merged. Thanks for your work on this! If anyone writes publically available plugins that make use of this API, please feel free to mention them in a comment for visibility....

> I’m very glad that this PR was accepted - now, instead of supporting my own fork, I just moved everything I needed into separate extensions: > > * [CMake...

Sent out https://github.com/clangd/vscode-clangd/pull/653 so the API appears in a vscode-clangd release

At the protocol level, clangd does support the client specifying compile commands via `workspace/didChangeConfiguration` messages (see https://clangd.llvm.org/extensions#compilation-commands for details), as an alternative to using `compile_commands.json`. The part I'm less sure...

Thanks for checking. Are you interested in writing a patch that implements the desired API?

At the protocol level this is caused by the affected diagnostics having the `Deprecated` [diagnostic tag](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#diagnosticTag) attached to them.

So one way to disable it in vscode is to set `"editor.showDeprecated"` to false. > preferably while maintaining the strikethrough behavior for deprecated code Does the "deprecated code" situation apply...