Catching Up with the Rust Content Team: RustWeek Interviews and a New Changelog Series
Back in May, RustWeek 2026 brought together the Rust community for a week of talks, workshops, and the Rust Project’s second All-Hands. Along with it, the Rust Project Content Team hosted some excellent conversations with Rust Project members. The entire set of videos is worth your time if you’re curious what’s actually happening on the ground across the Rust Project, straight from the people doing some interesting work.
I wanted to highlight a couple here because they touch on two areas where Rust is actively pushing into new territory: interoperating with existing C++ codebases, and meeting the bar for safety-critical software.
Teor on Rust-C++ Interoperability
Rust Lang Team Lead Tyler Mandry talks with Teor, C++ Interop Engineer at the Rust Foundation, about the ongoing effort to make Rust and C++ play nicely together. Teor shares a great story from their work on the Tor project (how an early experiment integrating Rust into a legacy C codebase eventually snowballed into a full distributed systems rewrite) and what that experience taught them about how Rust’s safety properties show up in real-world privacy and security software.
The conversation also touches on some recent work in the Rust Foundation’s Interop Initiatives (supported by Platinum Member, Google):
- Problem space mapping: an effort to document the exact use cases and pain points developers run into when interfacing Rust with foreign languages
- The “splat” overloading experiment: exploring how to make function overloading ergonomic for C++ FFI without compromising Rust’s trait coherence rules — more on this in a blog post from Teor, coming soon!
- Early feedback from an informal interop user study, which surfaced common onboarding hurdles like link errors and type mismatches.
If interop is something you want to help shape, join the discussion in #t-lang/interop on the Rust Zulip.
Pete LeVasseur on Safety-Critical Rust
In this second interview, Tyler Mandry talks with Pete LeVasseur, Lead of the Safety-Critical Rust Consortium, co-lead of the Eclipse Software Defined Vehicle’s Rust Special Interest Group, and a committer to Eclipse uProtocol, about what “safety-critical” actually means in software, why domains like cars and airplanes hold code to such a high standard, and the movements currently pushing Rust into these spaces.
If you work anywhere near safety-critical systems, this is a good primer on where Rust stands in this space today and where it’s headed.
These two videos are just a small sample of the full list of interviews from RustWeek 2026 from the Content Team. View them all on the Rust language YouTube channel.
More from t-content
The Content Team also just kicked off a new Rust Release Changelog series, hosted by Chris Biscardi, Cameron Dershem, and Pete LeVasseur. The first episode walks through what shipped in Rust 1.97.0, from v0 symbol mangling and cargo’s new support for denying warnings, to a deep dive on the never type, atomics and alignment, platform tiers, and a look at how the Compiler and Clippy teams collaborate. It’s a good watch if you want the “what changed and why it matters” version of a release. Stay tuned for the next release (and video!) on August 20th.
The Content Team has a lot of excellent material in the works, and we’re planning to highlight more of it here on a regular basis!
About the Rust Project Content Team:
Rust Content Team (t-content) records and produces interviews like the ones listed above to share with the wider Rust community. If you’re interested in contributing, have an idea for content, or want to be interviewed yourself, check out the content-team repo on GitHub or reach out on #t-content on the Rust Zulip.
