Nathan Ridge

I wonder if this would need a new inlay hint kind, or it can be considered a "type hint". (Technically, the thing being hinted is not a type, it's a...

> Has anyone actually tested with this option? There was a user I helped recently on Discord who fixed some error diagnostics by manually re-adding the GCC built-in include directory...

Here is a second example of a user in a similar situation: https://github.com/clangd/vscode-clangd/issues/639

> I do not see a use-case where someone would want to inspect clangd's implementation of a header when the code is compiled using a different implementation, such as gcc....

There is not. The current way to configure clangd to use a different compiler's built-in headers is to add their include path manually, e.g. using the [config file](https://clangd.llvm.org/config.html#compileflags): ```yaml CompileFlags:...

@kammce It's not clear from the description of the problem in the previous comment that you're running into the issue being discussed in this thread. Could you attach [clangd logs](https://clangd.llvm.org/troubleshooting.html#gathering-logs)?...

One other thing worth noting is that in the code completion popup, the signature is rendered as `f(A self, int arg)`. That doesn't tell you that the first parameter is...

> Cant find clangd's own logs. Please see https://clangd.llvm.org/troubleshooting.html#gathering-logs for how to do that.

Those are client-side logs. Could you try in VSCode, and follow the instructions I linked to?

> VSC: https://0x0.st/8E14.log I'm not seeing clangd produce any error diagnostics in this log. What file are you seeing error diagnostics in?