Our great sponsors
-
kok.nvim
Fast as FUCK nvim completion. SQLite, concurrent scheduler, hundreds of hours of optimization.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
coc.nvim
Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
-
-
-
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.
-
On my Neovim setup, I simply have the following plugins. I use paq as a plugin manager:
Coq_nvim
neovim/nvim-lspconfig
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.
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.
So, let's clarify a couple things first about how the Rust and Cargo crates work. First off, there is no single company or entity who's the sole contributor to the core Rust tooling. Rust is an open source project to which anyone can view the codebase and contribute (though there's a select set of people who are responsible for approving changes to it and managing releases). It's worth noting this doesn't mean there isn't an organization responsible for the project however. The Rust Foundation are a non-profit who manages the core repositories and tooling, and is also responsible for setting high level goals for the language.
I'm not sure what your previous programming experience is, but for a fully compiled language, Rust has some of the most easy to use cross compilation tooling of any language I've used. The rust compiler supports a lot of different architectures and a good number of things work out of the box without any special sysroots or anything. Many things do require setup, particularly anything that needs a system library. For that, I recommend checking out the cross project. It'll help you a lot.
Plugins for my neovim setup https://github.com/jroddev/dot-files-2022/blob/master/roles/neovim/files/lua/plugins.lua I moved from Clion to this for Rust and haven't needed to go back.
