In May 2026, 166 Rustaceans gathered in Utrecht for the Rust All Hands. This event is an opportunity for the Rust Project members and invited guests to work on Rust in person for several days — discuss its future, resolve blockers, build connections between teams, and so on (but not make any final decisions!).

This was the second All Hands organized by RustNL, after the one last year revived the tradition after a six-year hiatus. It was part of RustWeek both times, with the Rust All Hands following directly after the conference days. And yes, the All Hands will happen again in 2027! More details on that at the end.

Also co-located with the All Hands was the RustWeek Unconference, where invited ecosystem maintainers and contributors collaborated with each other and with Rust Project members. This year, there were six participating groups: Bevy Engine, Ariel OS, Linebender, the Safety-Critical Rust Consortium, Rust GPU, and Rust Embedded — with around 60 members in total.

Similarly to last year, the conference day right before the All Hands had a special track, the "Rust Project Track", with talks presented by Project members. (See the recordings.). The talks touched on some of the topics that the Rust teams discussed in greater depth in the All Hands sessions.

Sessions

At the All Hands, there were 73 sessions spread across 3 days and 11 rooms, most of which were pre-scheduled, though some happened spontaneously. You can find the session notes in rust-lang/all-hands-2026.

The State of the Rust teams session kicked off the All Hands and provided a (literal) platform for teams to tell everyone about their activities.

Many sessions focused on pressing topics in the Project's governance. The Leadership Council and Project Directors both held Q&A panels about their roles and processes, and how they relate to one another and the Rust Foundation. The moderation panel provided a safe space for Rust moderators to discuss the challenges they face, with support from Q (head moderator of Hachyderm)¹. The Project culture discussion examined sources of disempowerment for maintainers and contributors, and ways to address them. The sessions on Project Goals, north stars, and funding looked at improving how the Project coordinates and communicates work². Finally, there was a discussion about improving the RFC process, possibly by integrating some ideas from the TC39 process.

As expected, most of the sessions focused on the evolution of Rust itself. The teams discussed a wide variety of efforts, including const generics, const traits, field projections³ and reborrowing⁴ (1, 2, 3), in-place initialization, SIMD, allocators⁵, custom lints, stability attributes for libraries, rustc as a library⁶, the Sized Hierarchy, and auto traits. Beyond these, there were numerous sessions on compiler internals, codegen, semantics, specification, tooling, and infrastructure.

Interoperability was another prominent topic. Discussions covered the overall Rust/C++ interop problem and solution space⁷, the state of Rust/C++ interop using Crubit⁸, and safer interop via combining LLVM IR with Rust MIR. It was also great to see in-person collaboration between the Rust Project and both Rust for Linux⁹ and Rust for CPython, aimed at unblocking further integration of Rust into the Linux kernel and CPython.

Feedback

Overall, people loved the All Hands! Responders rated it 9.5/10 on average, and indicated they'd return next year if given the chance.

Here are some of the things they shared:

Got some very awesome conversations about effects with Jana Dönszelmann and later Tyler Mandry and Benno Lossin which have gotten me very excited and I'm writing blog posts as we speak.

I'm also full of ideas from the mods convo with Q, that I expect to bear fruit in subtle ways.

We may also have unblocked rustc_public, and are working with t-infra to be able to statically compile a rustc driver.

— Nadrieril

The week was full of good surprises! I was surprised at the significant interest in the things I'm working on, based on conversations and the attendance at the workshops (and the related talks).

I was happy to see we're covering most of the high priority interop issues people are concerned about. That was a really good outcome.

There are also a bunch of exciting things in the early stages of discussions or scoping work. Some might never happen, but if/when they are ready, I'm looking forward to sharing them.

— teor

For cargo-semver-checks, we decided on a path forward for building rustdoc JSON with correct features enabled, which is sufficient to unblock cross-crate analysis. We also agreed that it would be desirable to run it on PRs to the standard library, because accidental breakage happens there too and it's extremely painful to deal with. We have a clear path forward here too.

We also got to consensus that it would be good to ship (on stable) a rustup component with the rustdoc JSON of that target triple's standard library, while making the component itself unstable because the JSON format is not stable. This is a fine line, and we technically only just nailed down the details earlier this week, but the bulk of the spicy conversations happened in person.

I have more, these are just the first things that came to mind. I have probably a year and a half's worth of stuff to build off of just things that got unblocked at RustWeek. Now I just need more hours in the day to code! :)

— Predrag Gruevski

In addition to all the value the Rust Project got out of the "official" portions like the talks, All Hands sessions, etc. I also wanted to give one example of "I randomly bumped into someone in the hallway / at the hotel, and learned something invaluable as a result." It was a stroke of good fortune that I happened to bump into the right people, in the right context, to learn about that obscure edge case that will make cargo-semver-checks a more useful tool for the Rust community. This was far from the only such case at the All Hands!

There's inherent value in having people in the same place, and in facilitating opportunities for informal mingling — whether it's in hallways, at the post-event social sessions, at the hotel(s) where many people are staying, etc. I'm thrilled that the organizing team again paid a lot of attention to creating such opportunities in many ways: with the choice of venue, with how the schedule was created, with offering recommended hotel blocks that were relatively close to each other, etc.

— Predrag Gruevski

I covered so many different and varied topics, from meta-dictionary trait solving with lcnr & the rest of t-types over formality discussions with tiif, Xiang & Nico to talking with Aapo about reborrowing and so many more! (Not to mention the huge amount of people I talked with about field projections!) I feel bad making a list, because inevitably I would forget people, because it was so packed!

— Benno Lossin

my highlight on the technical side is definitely that we seem to have finished the non-aliasing-model parts of the opsem. :) specifically, reference and union validity. FCPs are in progress.

We didnt make as much progress on terminology as I had hoped, though we did uncover new interesting questions which is at least some progress.

— Ralf Jung

I'm thrilled that we settled union operational semantics at the All Hands.

I really appreciated the random conversations with people I didn't know. I'm glad that the event provides a low-friction way for Rust team members to make themselves available to others. :heart:

Oh, another one! I loved the "state of the teams" session (thanks to Lori Lorusso for coordinating it). I know it kinda ballooned with the addition of more teams, and I'm glad it did; I loved having a quick overview of the state of many different teams, including teams I haven't had much view into before.

— Josh Triplett

As someone totally new to the Project getting to meet people in person was really good and totally overwhelming but in a good way. I really enjoyed getting to have discussions with so many different people about a variety of rust and non rust topics. I really appreciate and can't thank the team reps enough that not only supported my session but created it (no way it would have worked if you all didn't step up to the stage) and for Mara giving me the opportunity to thank everyone in the closing session. This event and Mara's support did a lot for me and for what my position hopes to achieve.

— Lori Lorusso

Myself being fairly new, I went in not expecting much beyond just wanting to meet everyone, have a good time and watch people do their thing. But I contributed a fair amount to some meetings and had some very nice and productive 1:1 chats. It's also a totally different feeling contributing to rust now when you've met so many people IRL. 100% would do again.

— mejrs

I was at the unconf rather than the all-hands, but I just wanted to say it was a fantastic experience! Having the two events co-located was great for the ability to build connections between ecosystem and project people and work on problems and solutions together. Everyone I interacted with from the project was incredibly friendly and enthusiastic and projected an infectious can-do attitude about making Rust better. As this was my first-time at a Rust event, I came in feeling a bit intimidated about being in the same building as all these brilliant people who have done such impactful work, and I left feeling welcomed, included, and excited for next year.

— Jonathan Keller

All Hands 2027

The Rust All Hands will return next year! It will be part of RustWeek 2027 in Utrecht, the Netherlands, on 27–29 May.

Save the date, and we'll be sharing more information later!

Huge thanks to Mara and RustNL for keeping up this amazing tradition with such a deep level of care.

See you next year!