Nathan Ridge
Nathan Ridge
> has there been any news on this since 3 years ago? Clangd is an open-source project, with development happening in the open. As a general rule, if there is...
Released in 0.1.30.
@strpbrk just to confirm my understanding, this patch has the issues described in [this comment](https://github.com/clangd/vscode-clangd/issues/262#issuecomment-1308565341), and is thus not suitable to be reviewed and merged in its current form, right?
> @HighCommander4 it has at least those issues. More issues may have been introduced with API changes over the years, which I have not tracked. If I ever make time...
Please have a look at https://clangd.llvm.org/faq#why-does-clangd-not-return-all-references-for-a-symbol
Please follow the instructions at https://clangd.llvm.org/troubleshooting#getting-stacktraces-from-crashes to get a symbolized stack trace, so we can tell what function the crash is occurring in.
(Transferred to server repo, this is not specific to the vscode client.)
Clangd only runs the compiler's frontend on open files, while optimization remarks are produced by the backend. Given the performance implications of running the backend (as detailed more in the...
Can you share the relevant code files in text form?
Thanks. This is the same underlying issue as #206 (and #1101, #1673): clangd does not support well multiple symbols with the same name in a single workspace.