lsp-inlayhints.nvim VS coc-rust-analyzer

Thanks for the reply! I also wanted to make it work with clangd, but it won't. I stumbled upon this issue. Maybe you have enough knowledge to figure this out, I don't know how to set up this compilation database. I installed clangd using Mason, and configured it via lspconfig basically the same way as the guy in the issue I linked did. Also, I'm using the newest nightly.

I don't understand why inlay hints must be implemented in a rust-specific plugin. https://github.com/lvimuser/lsp-inlayhints.nvim exists, has support for inline inlay hints (on a separate branch for now) and works with rust (and should work any language server since inlay hints are part of the spec). Am I missing something?

To use inlay hints in typescript an rust you would need this plugin: https://github.com/lvimuser/lsp-inlayhints.nvim It provides example in the readme on how to setup inlay hints for typescript and rust. For now the master brach has "old" inlay hints implementation but there is a branch that implement new one. And of course you will need nightly version for that for now.

https://github.com/lvimuser/lsp-inlayhints.nvim (Multiple langs)

But it doesn't seem to work. I also tried lvimuser/lsp-inlayhints.nvim with no luck. Any advice of how to properly enable this feature when ocamllsp server is attached? Thank you in advance.

I have inlay hints working in nvim with lvimuser/lsp-inlayhints.nvim, no special configuration other than the LspAttach block from their README. The caveat is that your LSP server has to support inlay hints.

The second one might be https://github.com/lvimuser/lsp-inlayhints.nvim

you can use nvim-lspcofig for LSP support, mason.nvim for installing LSP servers, linters, formatters and debug adapters. nvim-cmp for completions, luasnip for snippets, null-ls for configuring your formatter and linters , lsp-inlayhints for inlay hints.

Inlay hints are available through rust-tools.nvim, or lsp-inlayhints.nvim.

iirc, inlay hints aren't supported by nvim's built-in LSP, but you can get them with the inlay-hints plugin: https://github.com/lvimuser/lsp-inlayhints.nvim (if the LSP for omnisharp also supports them)

Rust

You can absolutely get nvim and rust analyzer working together. I personally use this: https://github.com/fannheyward/coc-rust-analyzer

nvim plugin](https://github.com/neoclide/coc.nvim) together with the rust analyzer plugin. It's given me the most complete, useful experience developing in rust on nvim. I absolutely love it and can't recommend it enough.

I use https://github.com/neoclide/coc.nvim with https://github.com/fannheyward/coc-rust-analyzer and this default config: https://github.com/ithinuel/dotfiles/blob/main/.config/nvim/coc-settings.json#L2-L9

If you're using coc-rust-analyzer, did you try setting rust-analyzer.inlayHints.enable to false?

Using this plugin I have installed several extensions like coc-clangd and coc-rust-analyzer .

It works pretty well with coc-rust-analyzer actually. but I eventually found the file tree in VSCode very useful, also the debugging interface, so I use VSCode with the Vim plugin. It is the best of both worlds how I feel.

I would install coc.nvim and https://github.com/fannheyward/coc-rust-analyzer

Yeah sorry I thought you were saying to use the rust-analyzer vim plugin.

VIM users too! It is available as a language server extension for CoC, called coc-rust-analyzer and it works just as well as the VSCode version.