Still seeing too many Rust devs bogged down by slow LSP or clashing plugins. The ecosystem has stabilized. Here's the minimal stack that works without performance hits on Neovim 0.10+.
Core setup:
```lua
-- LSP & Completions
'mason.nvim',
'mason-lspconfig.nvim',
'nvim-lspconfig',
'neodev.nvim', -- critical for proper lspconfig setup
{
'rust-analyzer/rust-analyzer',
ft = 'rust',
build = 'cargo install --locked rust-analyzer'
},
{
'hrsh7th/nvim-cmp',
dependencies = {
'hrsh7th/cmp-nvim-lsp',
'hrsh7th/cmp-path',
'L3MON4D3/LuaSnip',
'saadparwaiz1/cmp_luasnip'
}
},
-- Syntax & Debugging
'rust-lang/rust.vim', -- for `cargo` commands and basic highlighting
'mfussenegger/nvim-dap',
```
Key config point: `neodev.nvim` must be set up *before* `lspconfig`. Prevents a class of Lua LSP errors that break Rust Analyzer.
Avoid these common conflicts:
- Multiple Rust syntax plugins (e.g., `vim-rust` alongside `rust.vim`)
- Running `coc.nvim` alongside `nvim-lspconfig` for Rust
- Old treesitter parsers that aren't built with `lockfile v3`
If your `:LspLog` shows continuous restarting, check for `cargo` metadata mismatches. Often a `Cargo.lock` issue, not a plugin issue.
Performance baseline: `rust-analyzer` memory should stay under 1.5GB on average projects. If it balloons, you likely have a workspace inclusion problem. Set `rust-analyzer.server.extraEnv` to `{ "RA_INTERNALS_SPAN_TABLE_CAPACITY": "256" }` in your LSP settings.
mw
Infrastructure is code.