Rust 2026 全员大会回顾
Rust All Hands 2026 Retrospective

原始链接: https://blog.rust-lang.org/inside-rust/2026/07/31/all-hands-2026-retrospective/

2026年5月,166名成员及嘉宾齐聚乌得勒支参加 Rust All Hands 大会,这是一场聚焦 Rust 编程语言未来的协作活动。该活动是 RustWeek 的一部分,由 RustNL 组织,为期三天的活动通过 73 场会议促进了深入的合作,并为生态系统维护者举办了同期举行的非正式会议(Unconference)。 主要讨论议题涵盖项目治理、文化与可持续性,以及对编译器内部机制、互操作性(包括 C++ 和 Linux 内核集成)的深度剖析,还有诸如常量泛型(const generics)和自定义 lint 等语言演进话题。与会者强调,此次活动的核心价值在于通过即兴的走廊交流和协作会议,打破障碍并建立人际联系。 此次活动获得了极好的反响,与会者表示在长期以来的技术难题上取得了突破,并改善了跨团队协作。鉴于此次成功,Rust All Hands 将于 2027 年 5 月 27 日至 29 日重返乌得勒支举办 RustWeek 2027。这一传统被证明对项目的发展至关重要,它使贡献者能够同步工作、解决复杂的开发任务,并加强社区的协作文化。

这篇 Hacker News 讨论帖探讨了 Rust 开发的现状,重点关注 GPU 和嵌入式生态系统,并围绕编译时间展开了辩论。 关于 GPU 支持,有批评者质疑为何“Rust-GPU”的关注度高于 Cudarc 或 WGPU 等更“可行”的工具。对此,一位维护者解释称,Rust-GPU 的目标是实现硬件层面的原生语言支持,而非仅仅是宿主端的绑定,并指出该生态系统目前规模较小,且尚未得到 Rust 核心项目的强力支持。 讨论帖还强调了嵌入式 Rust 社区内部的紧张关系:一些从业者认为,工作组更倾向于推崇复杂的、高度依赖 trait 的抽象,而非注重实用的、低门槛的固件开发。 最后,讨论还触及了 Rust 未来的采用前景。尽管一些用户担心随着大模型驱动开发的发展,缓慢的编译速度可能会阻碍 Rust 的推广,但资深开发者认为 `cargo check` 可以缓解这些瓶颈。他们认为,开发效率的真正限制因素依然是人的迭代速度,而非等待编译器的时间。
相关文章

原文

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.

A large room full of Rustaceans and friends smiling into the camera

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.

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.

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

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!

联系我们 contact @ memedata.com