this-week-in-rust VS rust-analyzer

In addition to these repositories, there's a valuable resource that no Rust enthusiast should overlook— This Week in Rust. This community-driven initiative aggregates Rust-related news, updates, and most importantly, a curated list of issues across various Rust projects. If you're on the lookout for a tailored contribution or seeking the perfect project to kickstart your open-source journey, This Week in Rust is your go-to source.

If you'd like to know the upcoming meetings - there are quite a few online meetings that you can attend regardless of your location - then check out This week in Rust

The This Week In Rust newsletter has a Call for Participation section where projects post requests for contribution.

“This week” train!

I’ll go next

This week in Rust

https://this-week-in-rust.org/

Currently I have This Week in Rust and lime's

There's some latency involved, but we have this week in rust for this exact reason. Also feel free to discuss the news on the comments page.

https://this-week-in-rust.org has a Call for Participation section.

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

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.

6. Rust Analyzer

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.

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.

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".

All I want to know is: Will it have a build configuration pulldown?

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.

rust-analyzer > manual > helix > binary > rustup component add rust-analyzer