[clangd-dev] Are there plans to support textDocument/implementation?

[Jonathan Gold via clangd-dev]

Thanks for the work on clangd. I'm using it now on macos for a c++
project, along with vim8 and the LanguageClient
(https://github.com/autozimu/LanguageClient-neovim) client, with
compile_commands.json generated via
https://github.com/grailbio/bazel-compilation-database .

Everything seems to work end to end, and even without indexing, things
like textDocument/definition and code completions work very quickly.

The one thing I seem to be missing is whether/how to use clangd via the
LPS client to go from a function call under the cursor to its actual
implementation (not just its definition). I assume that that would be
via textDocument/implementation
(https://microsoft.github.io/language-server-protocol/specification#textDocument_implementation),
but IIUC, that method is not implemented in clangd.

Is there some other method that I should be using? If not, are there
plans to implement this?

Apologies too if this list is not the correct place for this. I didn't
want to file this yet as a bugzilla bug if in fact it is a known issue
already. I tried searching bugzilla for "textDocument" and only saw one
result (https://bugs.llvm.org/show_bug.cgi?id=34497), so figured that
might not even be where features like this are requested.

jonathan