duct.rs VS coc-rust-analyzer

There is also duct which is not so much geared towards writing an interpreter, but does provide simplified macros for running subprocesses.

This doesn't address the generate-and-build step, but you can probably accomplish that by shelling out (perhaps with duct) to cargo build assuming your runtime environment has the necessary tools installed.

As mentioned by /u/llogiq, std::process::Command will work if you mean shelling out to another binary, but I wanted to point out the crate duct which makes this kind of thing simpler to handle.

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.