coc-marketplace VS coc-rust-analyzer

Here's a list of some available plugins: https://github.com/neoclide , however you can find even more if you install this: https://github.com/fannheyward/coc-marketplace . (coc.nvim is a vim plugin that *itself* has a long list of plugins, that support multiple languages / LSP clients. coc-marketplace is even more "meta", in that it is a coc.nvim plugin, that helps you find other coc.nvim plugins, LOL.) Anyways, point is, there's a LOT you can do with coc.nvim and a LOT can configure - but only if you CHOOSE to. :)

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.