vscode-rust
rust-analyzer
Our great sponsors
vscode-rust | rust-analyzer | |
---|---|---|
8 | 132 | |
1,401 | 13,551 | |
- | 1.7% | |
4.4 | 10.0 | |
over 1 year ago | 3 days ago | |
TypeScript | Rust | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
vscode-rust
-
Pinecone: Rust – A hard decision pays off
> it crashes process IDs more often than Justin Bieber crashes Maseratis: https://github.com/rust-lang/vscode-rust/issues/890
So -- this guy used an extension (named Rust) with rust-analyzer, which was known to not work, and it didn't work(!), and the Rust extension author recommends he tries the extension made for rust-analyzer. That extension doesn't have the features he likes (it works for me and has loads of features, so I have no idea what this is about?), and so they close the issue?
Hardly a case for the ages. Guy uses unsupported config and things don't work?
> What clangd does is work.
Don't doubt it. I'm just saying -- I haven't had any problems with the rust-analyzer extension since it became the Rust default. But, yes, I had a few hiccups and crashes beforehand, no doubt. I just have to imagine it's both younger, and doing more/different things than clangd.
-
RLS Deprecation | Rust Blog
I know. It's been argued for a long time. But at least if you follow the advice to install RA, it's fine. And if you don't, you won't be able to install RLS anyway, but instead get a helpful message pointing to RA.
-
rust-analyzer changelog #113
But the last commit to the Code extension was almost one year ago (an URL update), a pull request for a pretty annoying issue was not merged in more than a year, and the only activity on the issue tracker is people complaining about old issues and sometimes me asking them nicely to try rust-analyzer instead (but only when I'm pretty certain that their issue does not happen in RA).
-
rust-analyzer changelog #102
It's been asked before: https://github.com/rust-lang/vscode-rust/issues/927. Basically, rust-analyzer is not (yet?) a rust-lang.org project and it's not even going to be mentioned in the official docs until that happens.
-
rust-analyzer changelog #59
Yeah, see e.g. https://github.com/rust-lang/vscode-rust/issues/880.
-
rust-analyzer changelog #56
RA will be merged with the vscode-rust extension and aims to replace RLS (tracking issue on the vscode-rust repo).
rust-analyzer
-
Cranelift code generation comes to Rust
go build 3.62s user 0.76s system 171% cpu 2.545 total
I was looking forward to parallel front-end[4], but I have not seen any improvement for these small changes.
[1]: https://github.com/rust-lang/rust-analyzer
-
A guide on Neovim's LSP client
For example, intelephense can show diagnostics in real time, there is no need to save the file to get new diagnostics. But rust-analyzer, the language server for rust, can only update diagnostics after saving the file.
-
Top 10 Rusty Repositories for you to start your Open Source Journey
6. Rust Analyzer
-
The rust-analyzer vscode extension is not working at all.
The rust-analyzer readme suggests you go here for support request. But even there, you'll need to provide more details to get useful help.
-
LSP could have been better
For example: https://github.com/rust-lang/rust-analyzer/blob/master/docs/...
> If you create an LSP, it will work best in VS Code.
Any editor can work just as well as (or even better than) VS Code.
-
Discussion Thread
So, apparently the reason why rust-analyzer, the LSP server for Rust does not have persistent caching is because it would make "optimizing initial passes less important".
- The AI Content Flippening
-
Introducing RustRover – A Standalone Rust IDE by JetBrains
All I want to know is: Will it have a build configuration pulldown?
-
Mastering Emacs: What's new in Emacs 29.1
I am not a Rust dev. It surely looks great.
However, from what I understand it seems to supply just a parser separate from the Rust compiler (https://github.com/rust-lang/rust-analyzer/tree/master/crate...) trying to keep up with Rust‘s development. So, in principle, it could have been just another treesitter parser plugin, too.
So, again, the LSP framework does not directly provide any magical benefit over a static parsing framework. All the semantic analysis capabilities stem from a good parser.
-
helix shows rust "language server exited"
rust-analyzer > manual > helix > binary > rustup component add rust-analyzer
What are some alternatives?
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
intellij-rust - Rust plugin for the IntelliJ Platform
syntax-highlighter - Syntax Highlighter extension for Visual Studio Code (VSCode). Based on Tree-sitter.
rustfmt - Format Rust code
vscode-debug-visualizer - An extension for VS Code that visualizes data during debugging.
sublime-rust - The official Sublime Text 4 package for the Rust Programming Language
RocksDB - A library that provides an embeddable, persistent key-value store for fast storage.
coc-rust-analyzer - rust-analyzer extension for coc.nvim
vscode-drawio - This unofficial extension integrates Draw.io (also known as diagrams.net) into VS Code.
eglot - A client for Language Server Protocol servers
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
typescript-language-server - TypeScript & JavaScript Language Server