31 Dec 2025

feedPlanet Mozilla

This Week In Rust: This Week in Rust 632

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.

Updates from Rust Community

Project/Tooling Updates
Observations/Thoughts
Rust Walkthroughs
Miscellaneous

Crate of the Week

This week's crate is wgsl-bindgen, a binding generator for WGSL, the WebGPU shading language, to be used with wgpu.

Thanks to Artem Borisovskiy for the suggestion!

Please submit your suggestions and votes for next week!

Calls for Testing

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.

Rustup

Let us know if you would like your feature to be tracked as a part of this list.

Call for Participation; projects and speakers

CFP - Projects

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 Bluesky or Mastodon!

CFP - Events

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 Bluesky or Mastodon!

Updates from the Rust Project

297 pull requests were merged in the last week

Compiler
Library
Cargo
Rustdoc
Clippy
Rust-Analyzer
Rust Compiler Performance Triage

Not a lot of changes this week. Overall result is positive, largely thanks to https://github.com/rust-lang/rust/pull/142881, which makes computing an expensive data structure for JumpThreading MIR optimization lazy.

Triage done by @panstromek. Revision range: e1212ea7..112a2742

Summary:

(instructions:u) mean range count
Regressions ❌
(primary)		 0.5% [0.1%, 1.7%] 11
Regressions ❌
(secondary)		 0.2% [0.1%, 0.5%] 6
Improvements ✅
(primary)		 -0.5% [-1.3%, -0.1%] 74
Improvements ✅
(secondary)		 -0.6% [-1.8%, -0.2%] 71
All ❌✅ (primary) -0.4% [-1.3%, 1.7%] 85

2 Regressions, 0 Improvements, 3 Mixed; 1 of them in rollups 37 artifact comparisons made in total

Full report here

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.

Tracking Issues & PRs

Compiler Team (MCPs only)

No Items entered Final Comment Period this week for Cargo, Rust, Rust RFCs, Leadership Council, Language Team, Language Reference 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.

New and Updated RFCs
Tracking Issues & PRs
New and Updated RFCs

Upcoming Events

Rusty Events between 2025-12-31 - 2026-01-28 🦀

Virtual
Asia
Europe
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.

Jobs

Please see the latest Who's Hiring thread on r/rust

Quote of the Week

what even is time?!?

- Ralf Jung on his blog

Thanks to llogiq for the suggestion!

Please submit quotes and vote for next week!

This Week in Rust is edited by:

Email list hosting is sponsored by The Rust Foundation

Discuss on r/rust

31 Dec 2025 5:00am GMT

30 Dec 2025

feedPlanet Mozilla

William Durand: My process for pitching projects as an engineer

This winter break has finally given me the mental space I needed, so I wrote another work-related article this month1, yay! This time, I'll focus on my personal process for pitching projects as an engineer.

Ever had a great idea at work but struggled to get it on the roadmap? As an engineer in an environment where product work is primarily driven by product managers, I've learned how to turn ideas into team priorities. The good thing is: there is no need to be a lead engineer for that!

From idea to proposal

Every project starts with an idea aimed at solving a specific problem2. Focusing on small, self-contained problems is much easier than tackling something that spans the entire product or system. Addressing larger problems becomes easier with experience and practice.

I mainly do some research and talk to people. Sometimes, as an engineer who enjoys coding, I might also do some initial "hacking" to explore the idea and uncover potential issues. Though not strictly necessary, I find this helpful for uncovering technical blockers (I also love making cool demos 🙈).

The goal of this phase is to move the idea from a vague notion to a solid, credible solution for a well-defined problem. From experience, neglecting this step often leads to a half-baked proposal that lacks clarity and fails to gain traction.

Gaining initial buy-in

My strategy for socializing and building support for an idea usually involves three groups: my peers, my Product Manager (PM), and my manager. I typically move from peers up to my manager, adjusting my approach based on the feedback I receive along the way. This iterative feedback process is essential to me. It stress-tests the idea and maximizes my chances of success, even if the initial concept requires significant revision.

I aim to convince one or two peers. The burden of proof is entirely on me to sell the idea, which is why the previous step is so important. When the idea moves to the broader team or to the PM, having a peer vouch for its value shifts the dynamic from one person's suggestion to a team-vetted proposal.

Once I have peer buy-in, I start a conversation with the PM. Product Managers are focused on business value, not engineering details. They usually need answers to the following questions:

I've found that a concise document3 outlining the final state and answering these specific questions works best for engaging the PM. This is convenient because it's the same format I use when approaching my peers, so I usually keep the same living document.

Securing manager approval

Once I have my peers and product manager on board, I approach my manager to discuss planning. In collaboration with the PM, my manager ultimately owns the team's roadmap.

This isn't the first time my manager hears about the idea, though. I maintain a proactive communication strategy, ensuring I give them a heads-up about developing ideas and significant technical explorations early. This prevents my manager from being caught off guard or, worse, hearing about a developing initiative secondhand from other stakeholders. It also allows them to provide early, high-level strategic guidance that might steer the proposal in a more productive direction before significant effort is invested.

The aim is to engage them at the right time: early for awareness and strategic input, and formally when a well-supported, high-quality proposal is ready for definitive planning and commitment.

Final thoughts

This is my approach to increase the chances of a project to make it onto our roadmap. Do note that this approach won't always succeed. Ideas are sometimes rejected, and that's okay.

With that said, I'd encourage interested folks to come up with what works for them, but that's probably a safe start. If you're one of them, remember that likely no one will care more than you do, so don't drop the ball!

  1. The previous article covered some challenges as a tech lead. ↩

  2. A few concrete examples in no particular order: porting a feature to a different platform, sunsetting a service, building an in-house feature to replace a third-party application. ↩

  3. Such a document is often referred to as a "1-pager" even if its length can exceed a single page. ↩

30 Dec 2025 12:00am GMT

24 Dec 2025

feedPlanet Mozilla

This Week In Rust: This Week in Rust 631

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.

Updates from Rust Community

Official
Newsletters
Project/Tooling Updates
Observations/Thoughts
Rust Walkthroughs

Crate of the Week

This week's crate is arcshift, an Arc replacement for read-heavy workloads that supports lock-free atomic replacement.

Thanks to rustkins for the suggestion!

Please submit your suggestions and votes for next week!

Calls for Testing

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.

Call for Participation; projects and speakers

CFP - Projects

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.

No Calls for participation were submitted this week.

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 Bluesky or Mastodon!

CFP - Events

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 Bluesky or Mastodon!

Updates from the Rust Project

475 pull requests were merged in the last week

Compiler
Library
Rustdoc
Clippy
Rust-Analyzer
Rust Compiler Performance Triage

Very quiet week, with essentially no change in performance.

Triage done by @simulacrum. Revision range: 21ff67df..e1212ea7

1 Regression, 1 Improvement, 3 Mixed; 2 of them in rollups 36 artifact comparisons made in total

Full report here

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.

Tracking Issues & PRs

Rust

Cargo

Compiler Team (MCPs only)

Leadership Council

No Items entered Final Comment Period this week for Rust RFCs, Language Team, Language Reference 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.

New and Updated RFCs

Upcoming Events

Rusty Events between 2025-12-24 - 2026-01-21 🦀

Virtual
Asia
Europe
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.

Jobs

Please see the latest Who's Hiring thread on r/rust

Quote of the Week

they should just rename unsafe to C so people can shut up

- /u/thisismyfavoritename on /r/rust

Thanks to Brian Kung for the suggestion!

Please submit quotes and vote for next week!

This Week in Rust is edited by:

Email list hosting is sponsored by The Rust Foundation

Discuss on r/rust

24 Dec 2025 5:00am GMT