Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I had a similar idea when I started learning . It worked for simple programs with simple types and specific examples. But I ended up just installing rust-analyzer after a while. Knowing the types you are working with helps a lot, autoimporting traits is also super helpful cause it saves you from going mad trying to guess which is the trait you need to import at a given moment. You don’t need to ditch neovim for vscode just to get lsp, as you said, it’s has a builtin lsp client. You may want extra stuff in neovim that you get in vscode by default, like inlay hints . That’s the only extra plugin I use but I know many people recommend this one too.
I had a similar idea when I started learning . It worked for simple programs with simple types and specific examples. But I ended up just installing rust-analyzer after a while. Knowing the types you are working with helps a lot, autoimporting traits is also super helpful cause it saves you from going mad trying to guess which is the trait you need to import at a given moment. You don’t need to ditch neovim for vscode just to get lsp, as you said, it’s has a builtin lsp client. You may want extra stuff in neovim that you get in vscode by default, like inlay hints . That’s the only extra plugin I use but I know many people recommend this one too.
Like I said, I've been using emacs for 35 years, and my config wouldn't likely be great for you: the whole thing is a goshawful mess. In particular, I've modified some core keybindings to be compatible with the emacs knockoff I learned on initially. That said, you're welcome to them if you want them: here.
You can absolutely get nvim and rust analyzer working together. I personally use this: https://github.com/fannheyward/coc-rust-analyzer