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? Tweet us at @ThisWeekInRust or send us a pull request. Want to get involved? We love contributions.

This Week in Rust is openly developed on GitHub. If you find any errors in this week's issue, please submit a PR.

Updates from Rust Community


Project/Tooling Updates


Rust Walkthroughs


Crate of the Week

This week's crate is rustdoc-types, a crate with types to deserialize Rustdoc's JSON output.

Thanks to Nixon Enraght-Moony for the self-ish suggestion.

Please submit your suggestions and votes for next week!

Call for Participation

Always wanted to contribute to open-source projects but didn't 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.

Updates from the Rust Project

363 pull requests were merged in the last week

Rust Compiler Performance Triage

Overall a positive week for non-incremental performance (roughly 0.5% faster), however, some >1% regressions on multiple incremental benchmarks, primarily due to #95563, which will hopefully be investigated in the coming weeks.

Triage done by @simulacrum. Revision range: 7355d971..43d9f3

2 Regressions, 5 Improvements, 4 Mixed; 0 of them in rollups 57 artifact comparisons made in total

Full report here

Call for Testing

An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization. The following RFCs would benefit from user testing before moving forward:

  • No RFCs issued a call for testing this week.

If you are a feature implementer and would like your RFC to appear on the above list, add the new 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.

Approved RFCs

Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

  • No RFCs were approved this week.

Final Comment Period

Every week the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.


  • No RFCs entered Final Comment Period this week.

Tracking Issues & PRs

New and Updated RFCs

Upcoming Events

Rusty Events between 2022-05-25 - 2022-06-22 🦀


North America



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.

Rust Jobs



SixtyFPS GmbH

Bionaut Labs


Tempus Ex

Tweet us at @ThisWeekInRust to get your job offers listed here!

Quote of the Week

This is the difference in approaches of the two languages. In C++ if the code is vulnerable, the blame is on the programmer. In Rust if the code is vulnerable, Rust considers it a failure of the language, and takes responsibility to stop even “bad” programmers from writing vulnerable code. I can’t stress enough how awesome it is that I can be a careless fool, and still write perfectly robust highly multi-threaded code that never crashes.

kornel on lobste.rs (with a caveat from ZiCog that Rust does not guarantee freedom from all vulnerabilities!)

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, andrewpollack, U007D, kolharsam, joelmarcey, mariannegoldin.

Email list hosting is sponsored by The Rust Foundation

Discuss on r/rust