rust-analyzer
| firewatch-theme-vscode | rust-analyzer | |
|---|---|---|
| 1 | 133 | |
| - | 13,727 | |
| - | 1.3% | |
| - | 10.0 | |
| - | 3 days ago | |
| Rust | ||
| - | 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.
firewatch-theme-vscode
-
I made a VS Code theme optimised for rust-analyzer based on a discussion here
I really like the Firewatch theme! The idea is great, but I find the colors hard to see right now. I'd love something with more contrast/colors that pop.
rust-analyzer
- Higher RAII, and the Seven Arcane Uses of Linear Types
-
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.
What are some alternatives?
vscode-rust - Rust extension for Visual Studio Code
intellij-rust - Rust plugin for the IntelliJ Platform
rustfmt - Format Rust code
sublime-rust - The official Sublime Text 4 package for the Rust Programming Language
coc-rust-analyzer - rust-analyzer extension for coc.nvim
eglot - A client for Language Server Protocol servers
typescript-language-server - TypeScript & JavaScript Language Server
vim-lsp-settings - Auto configurations for Language Server for vim-lsp
tree-sitter-rust - Rust grammar for tree-sitter
Neovim-from-scratch - 📚 A Neovim config designed from scratch to be understandable
intellij-lsp-server - Exposes IntelliJ IDEA features through the Language Server Protocol.
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/