Nathan Ridge
Nathan Ridge
Duplicate of https://github.com/llvm/llvm-project/issues/69690
Clangd's support for modules is known to be broken, and is actively being worked on in https://github.com/clangd/clangd/issues/1293. (The issue talks about "C++20 modules" and "clang header modules". I assume `@import`...
It's specifically `modernize-*` checks which get assigned a lower diagnostic severity (resulting in not being listed in the Problems panel) and the `Deprecated` diagnostic tag (resulting in the strike-through style)....
You might find some helpful tips in https://github.com/clangd/vscode-clangd/issues/125
> --cuda-path=/usr/local/cuda/bin/ > ... > -LC:/usr/local/cuda/lib64 That doesn't look right. `/usr/local/cuda/bin/ ` is a Unix path. `C:/usr/local/cuda/lib64` is a Windows path. What OS are you on?
> I’m on Ubuntu , Unix Ok, so `C:` should definitely not appear in the paths present in the compile flags.
This is just an artifact of how VSCode renders Markdown in hover popups. It does not indicate any error or problem.
Here is a previous issue that contains some discussion that may be relevant: https://github.com/clangd/vscode-clangd/issues/440
> I tried with the suggestion to open the file CPP file in background using vscode API "**vscode.workspace.openTextDocument**" and it does trigger **"textDocument/didOpen"** on the file and then calling the...
Can you attach a debugger to the clangd process at the time of the hang and get a stack trace?