Nathan Ridge

Could you specify what config / code change you're referring to? (And could you please do it in a comment on #300, to keep the discussion in one place? Thanks!)

Can you post verbose logs please (`--log=verbose` in `"clangd.arguments"`)?

Based on the log, standard library includes like `` are resolved fine. The issue seems to be that `bufmgr.h` is not a self-contained file (https://github.com/clangd/clangd/issues/45). It does not directly or...

One thing to determine to implement something like this is what is considered "unsupported". Is only the latest version considered supported? If so, how soon after the release of a...

So there is in fact only one `TurboModule.h` file in the filesystem? When you perform go-to-definition on `` vs. ``, does clangd open the same file (full path)? Is the...

Maybe part of the issue is that clangd's support for modules is known to be incomplete (https://github.com/clangd/clangd/issues/1293)

> I think this issue can be closed as --use-dirty-headers is now part of clangd I think the remaining open question is whether we should consider making this the default.

Have a look at `--query-driver`, as discussed at https://clangd.llvm.org/troubleshooting#cant-find-standard-library-headers-map-stdioh-etc (and in more detail at https://clangd.llvm.org/guides/system-headers#query-driver). Using it tends to fix these kinds of issues in cross-compilation scenarios. If it doesn't,...

> @HighCommander4 I tried to use the `--query-driver` option and from the logs it seems to be working, but nothing really has changed. Well, something has changed: at least some...

@catdotjs Have you tried the suggestion I made above about `--query-driver`? If you've tried it and it's not working, please feel free to share [clangd logs](https://clangd.llvm.org/troubleshooting.html#gathering-logs) for further diagnosis.