Forcing #Zed to use #beta of the #rust-analyzer for the project is neither trivial nor obvious. It by default calls stable rust-analyzer ignoring rustup's override for the project; on top of that installing rust-analyzer beta using #rustup is non-obvious and doesn't happen automatically with the override to the beta chanel to my disappointment.
Fact #Zed doesn't handle environment variables in settings files doesn't help.
another day, another #rustup install in Fedora Toolbox using the one internet blog that exists on the subject because otherwise nothing works
RE: https://social.rust-lang.org/@rust/116216894415467115
At this point, every #rustup release is another small victory worth celebrating 🥳
Many thanks not only to myself for making it all the way here, but also to the rustup team, the Rust org, and every single friend that has supported me through this journey, without your help this would never be possible 🙏
It’s been taking a while longer than expected, but I’m glad to finally announce this new #rustup beta release!
Following the footsteps of many other package managers, rustup now includes preliminary IO concurrency, and I’m quite excited about the potential performance boosts to come :)
Many thanks to my teammates @djc @chrisdenton, my GSoC buddy Francisco T. Gouveia, and all the other contributors who made this new release possible!
https://internals.rust-lang.org/t/seeking-beta-testers-for-rustup-v1-29-0/23814
Hi everyone! I'd like to announce on behalf of the rustup team that rustup 1.29.0 beta is now available for testing and we are currently looking for testers. The headline of this release is that rustup has been enabled to download components concurrently and unpack during downloads in operations such as rustup update or rustup toolchain, and to concurrently check for updates in rustup check, thanks to the GSoC 2025 event. This is by no means a trivial change so a long tail of issues might occu...