Info
This post is auto-generated from RSS feed This Week in Rust. Source: This Week in Rust 604
Category: This Week in Rust
Hello and welcome to another issue of This Week in Rust! Rust is a programming language empowering everyone to build reliable and efficient software. This is a weekly summary of its progress and community. Want something mentioned? Tag us at @thisweekinrust.bsky.social on Bluesky or @ThisWeekinRust on mastodon.social, or send us a pull request. Want to get involved? We love contributions.
This Week in Rust is openly developed on GitHub and archives can be viewed at this-week-in-rust.org. If you find any errors in this week's issue, please submit a PR.
Want TWIR in your inbox? Subscribe here.
This week's crate is RobustMQ, a next-generation, high-performance, multi-protocol message queue.
Thanks to Yu Liu for the self-suggestion!
Please submit your suggestions and votes for next week!
An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization.
If you are a feature implementer and would like your RFC to appear in this list, add a
call-for-testing
label to your RFC along with a comment providing testing instructions and/or
guidance on which aspect(s) of the feature need testing.
Let us know if you would like your feature to be tracked as a part of this list.
Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!
Some of these tasks may also have mentors available, visit the task page for more information.
If you are a Rust project owner and are looking for contributors, please submit tasks here or through a PR to TWiR or by reaching out on X (formerly Twitter) or Mastodon!
Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.
If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a PR to TWiR or by reaching out on X (formerly Twitter) or Mastodon!
461 pull requests were merged in the last week
param_env
canonicalizationcheck_id
MixedBitSet
for borrows-in-scope dataflow analysismul_add
now"file_lock"
featureVec::peek_mut
Clone
implementation for ChunkBy
fmt::Display
of 128-bit integers, without unsafe pointerbit_width
for unsigned integer typesBTreeSet::extract_if
cargo remove <TAB>
span_lint
in diagnostics.rsunbuffered_bytes
docs more consistentidentity_op
when encountering Default::default()
collapsible_else_if
FP on conditionally compiled stmtneedless_doctest_main
panic when doctest is invalidunit_arg
suggests wrongly for Default::default
manual_swap
manual_flatten
removes the useless if letClippyCtfe
pass#### Rust-Analyzer
ItemTree
's ItemVisibilities
has no identity, so deduplicateSelf
to the enum
name when possible+
in dyn trait typecargo metadata
impl
senum
variants querypub(crate)
and pub(self)
visibility resolutionEMPTY
item tree deduplicationItemTree
BlockId
into a #[salsa::tracked]
ThinVec
in ItemScope
in a couple placesRelatively quiet week, with a few improvements to benchmarks leveraging the new trait solver.
Triage done by @kobzol. Revision range: c31cccb7..45acf54e
Summary:
(instructions:u) | mean | range | count |
---|---|---|---|
Regressions ❌ (primary) |
0.3% | [0.1%, 0.5%] | 14 |
Regressions ❌ (secondary) |
0.3% | [0.1%, 0.5%] | 52 |
Improvements ✅ (primary) |
-0.5% | [-4.8%, -0.1%] | 68 |
Improvements ✅ (secondary) |
-4.3% | [-56.5%, -0.1%] | 85 |
All ❌✅ (primary) | -0.4% | [-4.8%, 0.5%] | 82 |
3 Regressions, 7 Improvements, 4 Mixed; 4 of them in rollups 51 artifact comparisons made in total
Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:
Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.
No Items entered Final Comment Period this week for Language Reference, Language Team or Unsafe Code Guidelines.
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
Rusty Events between 2025-06-18 - 2025-07-16 🦀
If you are running a Rust event please add it to the calendar to get it mentioned here. Please remember to add a link to the event too. Email the Rust Community Team for access.
Please see the latest Who's Hiring thread on r/rust
But after a few weeks, it compiled and the results surprised us. The code was 10x faster than our carefully tuned Kotlin implementation – despite no attempt to make it faster. To put this in perspective, we had spent years incrementally improving the Kotlin version from 2,000 to 3,000 transactions per second (TPS). The Rust version, written by Java developers who were new to the language, clocked 30,000 TPS.
This was one of those moments that fundamentally shifts your thinking. Suddenly, the couple of weeks spent learning Rust no longer looked like a big deal, when compared with how long it’d have taken us to get the same results on the JVM. We stopped asking, “Should we be using Rust?” and started asking “Where else could Rust help us solve our problems?”
– Dr. Werner Vogels on his blog
Thanks to Brian Kung for the suggestion!
Please submit quotes and vote for next week!
This Week in Rust is edited by: nellshamrell, llogiq, cdmistman, ericseppanen, extrawurst, U007D, joelmarcey, mariannegoldin, bennyvasquez, bdillo
Email list hosting is sponsored by The Rust Foundation
🏷️ rust_feed