Nathan Ridge

A similar issue was reported in https://github.com/clangd/clangd/issues/2221, [this comment](https://github.com/clangd/clangd/issues/2221#issuecomment-2498351363) is potentially interesting.

This indicates a project configuration issue. Have you followed the project setup steps at https://clangd.llvm.org/installation#project-setup? If you have, please share [clangd logs](https://clangd.llvm.org/troubleshooting.html#gathering-logs) for further diagnosis.

I suspect it's the `hover` request that takes long, probably due to some macro-specific processing (e.g. computing the expansion of the macro to show in the hover window) hitting some...

Looks like it may be not just `hover`, but any editor feature whose implementation uses `SelectionTree` invoked at the affected macro invocation. For example, I tried setting a breakpoint during...

> [ ] Document any notable new features on the clangd website I'm going to consider this checked off for clangd 20. I think the only major feature that would...

> [...] we don't have a section for call hierarchy at all. It would be nice to add one, under "Navigation" Filed https://github.com/llvm/clangd-www/issues/125 about this.

20.1.0 release is now up on Github: https://github.com/clangd/clangd/releases/tag/20.1.0

> 20.1.0 release is now up on Github: https://github.com/clangd/clangd/releases/tag/20.1.0 Now marked as stable (pre-release checkbox unchecked).

> Thanks. But it's not marked 'latest'. Yep, that's deliberate. Marking it at 'latest' rolls it out as an automatic update to all vscode-clangd users. I'd like to wait longer...

Apologies, I once again forgot to circle back to this and mark the 20.x release as 'latest'. I need a better system for remembering to do that... Anyways, done now,...