Interview
summary
Describes concrete work: Crubit is Google’s bidirectional C++/Rust tool aiming to make any crate callable from C++, already binding hundreds of crates and generating Rust bindings for thousands of C++ targets inside a monorepo that sits atop roughly a billion lines of C++. Covers real engineering choices—how async/await landed, why overloading matters for interop—and production experiments like hot swapped C++ functions with Rust implementations, plus which missing language ergonomics block wider adoption.
AI-written summary · about
chapters (14)
- 0:00Rust journey conversation
- 1:09Early Rust experiences
- 5:43Returning to Rust
- 8:11Rust community growth
- 10:00Prioritizing Rust work
- 13:49Rust features and design
- 16:28Async await trade-offs
- 20:19C++ and Rust interop
- 23:49C++ developer adoption
- 27:00Hands-on Rust features
- 30:57When Rust wasn’t right
- 35:09Rust in AI and systems
- 38:20Rust ecosystem gaps
- 42:15Closing thoughts
related talks
25mRust and C++
01h 11mDuck-Tape Chronicles - Rust C++ Interop
53mC++/Rust Interop: A Practical Guide to Bridging the Gap Between C++ and Rust
01h 02mRust/C++ Interop: Carcinization or Intelligent Design?
59mRust for C++ developers - What you need to know to get rolling with crates
52mBuilding Bridges: C++ Interop, Foreign Function Interfaces & ABI
37mDuck-Tape Chronicles: Rust/C++ Interop
31mFrom C++ APIs to Idiomatic Rust: Wrapper Design Patterns