rust
rust-analyzer
rust | rust-analyzer | |
---|---|---|
2,781 | 207 | |
100,984 | 9,320 | |
0.9% | - | |
10.0 | 10.0 | |
4 days ago | almost 3 years ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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
-
It Is Time to Standardize Principles and Practices for Software Memory Safety
The bug used by that repository [1] isn't the only one that can be used to escape the Safe Rust type system. There are a couple others I've tried [2] [3], and the Rust issue tracker currently lists 92 unsoundness bugs (though only some of them are general-purpose escapes), and that's only the ones we know about.
These bugs are not really a problem in practice though as long as the developer is not malicious. However, they are a problem for supply chain security or any case where the Rust source is fully untrusted.
[1]: https://github.com/rust-lang/rust/issues/25860
[2]: https://github.com/rust-lang/rust/issues/57893
[3]: https://github.com/rust-lang/rust/issues/133361
-
Roc Rewrites the Compiler in Zig
Since at least 2018, there's been a planned upgrade to the borrow checker to permit certain patterns that it currently rejects [0]. Also since 2018, there's been an implementation of the new version (called Polonius) that can be enabled with an unstable compiler flag [1].
But it's 2025, and the new version still hasn't been enabled on stable Rust, since the Polonius implementation is seen as too slow for larger programs. A big goal of the types team since last year has been to reimplement a faster version within rustc [2].
I'd count this as a language feature (albeit a relatively minor one) that's been greatly deferred in favor of shorter compile times.
[0] https://blog.rust-lang.org/inside-rust/2023/10/06/polonius-u...
[1] https://github.com/rust-lang/rust/pull/51133
[2] https://rust-lang.github.io/rust-project-goals/2024h2/Poloni...
-
Rust's worst feature (available in Rust nightly)
> Is there evidence more baking won't happen?
No, actually there is a lot of evidence that it will still be worked on.
Normally I would just say look at the issue linked in the nightly docs but due to an overlap of tacking PR and moving it from std to core PR it's not supper useful.
Tracking Issue: https://github.com/rust-lang/rust/issues/78485
If the author has constructive critique they should probably mention it there (after skimming through the discussion to make sure this wasn't already considered and not done due to subtleties they overlooked in the blog post (like e.g. that it's a standard/core feature which has to work across all targets and as such can't rely on anything being initialized to 0 by the OS, or that depending on the global allocator used you definitely can't rely on things being zeroed even if the OS only hands out zeroed memory, etc. etc.))
-
I've been advocating for RSS support, and you should too
I recently had the need to subscribe to changes to a Github repo and it turns out it provides a feed for them. For rust master branch, for example, subscribe to https://github.com/rust-lang/rust/commits/master.atom.
- Rust's New Sort Algorithms
-
KEON is a human-readable serde format that syntactic similar to Rust
With some notable exceptions. I'll never love the turbofish [1] for example.
[1] https://github.com/rust-lang/rust/blob/master/tests/ui/parse...
-
2025’s Must-Know Tech Stacks
Rust
- Loco 0.14 on Cathyos: 始め方
-
Loco 0.14 on Cathyos: Getting started
Loco is a relatively new Rust web framework which first appeared around 2021. It is strongly inspired by Ruby on Rails, and designed to bring developers productivity as various functionality on routing, middlewares, and request handling. They aim to provide a modern and intuitive development experience.
-
Getting Started with Blockchain: A Guide for Beginners
Developer: Learn programming languages like Solidity (Ethereum) or Rust (Polkadot).
rust-analyzer
-
rust-analyzer changelog #177
#14561 map tokens from include! expansion to the included file
- Make LSP-Rust-analyzer works
-
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.
What are some alternatives?
carbon-lang - Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
Odin - Odin Programming Language
vscode-rust
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
intellij-rust - Rust plugin for the IntelliJ Platform
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
sublime-rust - The official Sublime Text 4 package for the Rust Programming Language
hylo - The Hylo programming language
rustfmt - Format Rust code
Elixir - Elixir is a dynamic, functional language for building scalable and maintainable applications
vscode-rust - Rust extension for Visual Studio Code