Nathan Ridge

I can't spot anything wrong in what you've shown so far. Could you attach [clangd logs](https://clangd.llvm.org/troubleshooting#gathering-logs) as well? That will allow us to confirm that clangd is finding the `compile_commands.json`...

I agree this would be useful. Note, we already have #520 on file for the function signature part and there's some discussion of it there. If you'd like to work...

There were improvements made in this area in https://reviews.llvm.org/D96751. @rapgenic do you feel they have addressed this issue sufficiently?

Thanks for the comprehensive report and reduced testcase! I can confirm that I'm seeing the same problem. (In my case, what's extra fun is that my clang(d) is built with...

My tentative diagnosis above does seem to be consistent with the various symptoms reported: * Why it affects `#include_next`: the C file ends up with a combination of the queried...

> [Re gcc-toolchain: Sounds like you understand what's going on there much better than I, but thought I should cross-ref that clangd seems to choke on them when provided as...

Proposed patches: https://reviews.llvm.org/D133756 https://reviews.llvm.org/D133757 They also fix #1089 and #1173

Not specific to an editor, vscode has the same behaviour. #387 is related.

Moved to clangd repo since support for a code action like this would have to be implemented on the server side. For C++, a somewhat similar code action that exists...

Some other open bugs we have on file related to modules are #738, #797, #1105.