Nathan Ridge

Duplicate of https://github.com/llvm/llvm-project/issues/70930

> Hi @HighCommander4 could you please put some starting points / guidance here so anyone interested to implement this would have something to start with! Now that I take a...

> The release notes for each LLVM Release, that includes clangd, can be found here: https://releases.llvm.org/. Here is an example from 18.1.0: https://releases.llvm.org/18.1.0/tools/clang/tools/extra/docs/ReleaseNotes.html#improvements-to-clangd The 18.1.0 release notes on that page...

> Perhaps it could also be shown in the vscode extension when the version was bumped there, for more visibility. Note that vscode-clangd releases can be freely mixed with clangd...

@GitMensch That is #337. A workaround is to add `#pragma once` to both files. (Note also that the `#ifndef A_H` in `b.h` is redundant -- the include guard inside `a.h`...

Possibly related: #413, #197

> I have the same issue with `clang-tidy`. Now, `cmake` has started passing gcc specific flags for modules support, which breaks clang-tidy. Any solution? You may want to ask that...

(Moved to server repo)

I think this is an artifact of how the code is organized. It's something like this:  The diagnostic surfaced by clangd is coming from clangd's direct integration with include-cleaner,...

These command names do not come from clangd or vscode-clangd. They come from vscode itself, for example "Go to Type Definition" comes from [here](https://github.com/microsoft/vscode/blob/19ecb4b8337d0871f0a204853003a609d716b04e/src/vs/editor/contrib/gotoSymbol/browser/goToCommands.ts#L500). So, the right place to file...