Nathan Ridge

I debugged this a bit. The checker runs, but early exits [here](https://searchfox.org/llvm/rev/1bb8db5d5e1a3ea99525fd2648164a257955cd6d/clang-tools-extra/clang-tidy/bugprone/BadSignalToKillThreadCheck.cpp#55) while trying to determine the numerical value of the `SIGTERM` macro. That is in turn because when it...

With all that said, "determine the numerical value of an object-like macro defined in the preamble" is clearly a use case that otherwise works in clangd (e.g. when you hover...

I'm going to move this issue to the server repo now that we've confirmed that cause is not vscode-specific.

Perhaps we can compute the more expensive diagnostics for the open file as a lower-priority task that runs once clangd is idle?

Good points. I'll note that C++20 Concepts will alleviate this somewhat. In a situation like the above, where `foo()` cannot be instantiated with all types, a C++20 version of `foo()`...

Brainstorming a couple of related ideas: * As an alternative to an allowlist of headers, we could have an allowlist of function names. This would be more targeted and have...

I'm going to reopen this to signal that there are potential improvements to be made here, based on the more recent comments.

> I'm going to reopen this to signal that there are potential improvements to be made here, based on the more recent comments. (It appears I forgot to actually reopen...

Clangd 10 is now 11 releases old. A lot of things have been fixed and improvements made since then. Please try [clangd 21](https://github.com/clangd/clangd/releases/tag/21.1.0) and share logs from that if you're...

See also a related request (about runtime-unreachable code) at https://github.com/clangd/vscode-clangd/issues/435.