rust-analyzer
A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer] (by rust-analyzer)
neovim-rust
Sample neovim and vim configurations for Rust development (by sharksforarms)
Our great sponsors
rust-analyzer | neovim-rust | |
---|---|---|
207 | 5 | |
9,320 | 306 | |
- | - | |
10.0 | 0.0 | |
about 2 years ago | over 1 year ago | |
Rust | Vim Script | |
GNU General Public License v3.0 or later | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rust-analyzer
Posts with mentions or reviews of rust-analyzer.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-17.
-
rust-analyzer changelog #177
#14561 map tokens from include! expansion to the included file
-
Make LSP-Rust-analyzer works
return { tools = { -- autoSetHints = false, on_initialized = function() vim.api.nvim_create_autocmd({ "BufWritePost", "BufEnter", "CursorHold", "InsertLeave" }, { pattern = { "*.rs" }, callback = function() vim.lsp.codelens.refresh() end, }) end, auto = false, inlay_hints = { -- Only show inlay hints for the current line only_current_line = false, auto = false, -- Event which triggers a refersh of the inlay hints. -- You can make this "CursorMoved" or "CursorMoved,CursorMovedI" but -- not that this may cause higher CPU usage. -- This option is only respected when only_current_line and -- autoSetHints both are true. only_current_line_autocmd = "CursorHold", -- whether to show parameter hints with the inlay hints or not -- default: true show_parameter_hints = false, -- whether to show variable name before type hints with the inlay hints or not -- default: false show_variable_name = false, -- prefix for parameter hints -- default: "<-" -- parameter_hints_prefix = "<- ", parameter_hints_prefix = " ", -- prefix for all the other hints (type, chaining) -- default: "=>" -- other_hints_prefix = "=> ", other_hints_prefix = " ", -- whether to align to the lenght of the longest line in the file max_len_align = false, -- padding from the left if max_len_align is true max_len_align_padding = 1, -- whether to align to the extreme right or not right_align = false, -- padding from the right if right_align is true right_align_padding = 7, -- The color of the hints highlight = "Comment", }, hover_actions = { auto_focus = false, border = "rounded", width = 60, -- height = 30, }, }, server = { --[[ $ mkdir -p ~/.local/bin $ curl -L https://github.com/rust-analyzer/rust-analyzer/releases/latest/download/rust-analyzer-x86_64-unknown-linux-gnu.gz | gunzip -c - > ~/.local/bin/rust-analyzer $ chmod +x ~/.local/bin/rust-analyzer --]] -- cmd = { os.getenv "HOME" .. "/.local/bin/rust-analyzer" }, cmd = { os.getenv "HOME" .. "~/.cargo/bin/rust-analyzer" }, on_attach = require("user.lsp.handlers").on_attach, capabilities = require("user.lsp.handlers").capabilities, settings = { ["rust-analyzer"] = { lens = { enable = true, }, checkOnSave = { command = "clippy", }, }, }, }, }
-
rust-analyzer changelog #164
I would like changes like https://github.com/rust-analyzer/rust-analyzer/pull/13799 to be listed in 'Breaking Changes' category, to приманка draw the users' attention.
-
Mun v0.4.0 released
For those of you who haven’t heard of Mun before, Mun is an embeddable programming language empowering creation through iteration. The idea to create Mun originated out of frustration with the Lua dynamic scripting language and a desire to have similar hot reloading functionality available in Rust. As such, it’s not a direct competitor with Rust, but instead is intended to be used with Rust (or C/C++) as a host/embedded language pairing. Actually, Mun is completely written in Rust, building on similar crates as rust-analyzer and rustc. Its key features include:
-
rust-analyzer changelog #159
#13728 upgrade chalk to make solver fuel work again (works around most trait solving hangs).
-
rust-analyzer changelog #147
#13221 (first contribution) add option to move lenses above doc comments (rust-analyzer.lens.location):
-
Does Rust need proc-macros 2.0?
Rust-analyzer has a good overview: https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/dev/syntax.md
-
rust-analyzer changelog #134
#12517 (first contribution) fix completion for methods in trait generated by macro.
-
LSP Rust Analyzer keeps telling me `Error NO_RESULT_CALLBACK_FOUND`
-- all the opts to send to nvim-lspconfig -- these override the defaults set by rust-tools.nvim -- see https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#rust_analyzer server = { -- on_attach is a callback called when the language server attachs to the buffer -- on_attach = on_attach, settings = { -- to enable rust-analyzer settings visit: -- https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/user/generated_config.adoc ["rust-analyzer"] = { -- enable clippy on save checkOnSave = { command = "clippy" }, assist = { importGranularity = "module", importPrefix = "self", }, cargo = { loadOutDirsFromCheck = true }, procMacro = { enable = true }, } } },
-
rust-analyzer changelog #130
#12349 publish universal VSIX to make Code happy.
neovim-rust
Posts with mentions or reviews of neovim-rust.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-27.
- Config For rust dev
-
Setting up NeoVim in Rust?
If you're looking for a sample config, I recommend this one: https://github.com/sharksforarms/vim-rust/blob/master/neovim-init-lsp-compe-rust-tools.vim
-
Neovim - Why I'm switching to Native LSP over CoC
I tried neovim-init-lsp-compe.vim and neovim-init-lsp.vim from these minimal configs but no luck. I currently am all drained trying to debug my issues so might live with it or go back to vscode or coc. But I really really appreciate the work you guys do!
-
rust-analyzer features in neovim
And the repo for examples: https://github.com/sharksforarms/vim-rust
What are some alternatives?
When comparing rust-analyzer and neovim-rust you can also consider the following projects:
vscode-rust - Rust extension for Visual Studio Code
neovide - No Nonsense Neovim Client in Rust
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
nix-dotfiles - A graveyard of broken dreams.
intellij-rust - Rust plugin for the IntelliJ Platform
nvim-lspconfig - Quickstart configs for Nvim LSP
rustfmt - Format Rust code
coc-rust-analyzer - rust-analyzer extension for coc.nvim
eglot - A client for Language Server Protocol servers
typescript-language-server - TypeScript & JavaScript Language Server
rust - Empowering everyone to build reliable and efficient software.
rust-analyzer - A Rust compiler front-end for IDEs
rust-analyzer vs vscode-rust
neovim-rust vs neovide
rust-analyzer vs Clippy
neovim-rust vs nix-dotfiles
rust-analyzer vs intellij-rust
neovim-rust vs nvim-lspconfig
rust-analyzer vs rustfmt
neovim-rust vs coc-rust-analyzer
rust-analyzer vs eglot
neovim-rust vs typescript-language-server
rust-analyzer vs rust
neovim-rust vs rust-analyzer