Panel: Rust and C++ can work together!
summary
Panelists argue practical interoperability: Slint exposes a Rust core with C++ bindings and had to reimplement vtables so types stay idiomatic across languages, zbus is used instead of QDBus, and CXX/CXXc tooling automates many C ABI conversions. They show IPC boundaries via DBus or processes to isolate unsafe code, point to C++26’s trivially relocatable work as crucial, and note certification regimes like ISO26262 and ASIL and the slow RFC-driven evolution of Rust ABI features.
AI-written summary · about
chapters (10)
- 0:00Rust and C++ interoperability
- 1:04Hurdles in Rust-C++ interop
- 7:09Rust in automotive adoption
- 10:43Overcoming Rust resistance
- 16:03Community lessons learned
- 21:04Stability and ABI challenges
- 26:25Certification in safety-critical Rust
- 32:04Rust versus C++ rivalry myths
- 36:43Future of Rust and C++
- 41:42Closing remarks
related talks
01h 11mDuck-Tape Chronicles - Rust C++ Interop
38mPanel: Rust in reality
01h 02mRust/C++ Interop: Carcinization or Intelligent Design?
37mDuck-Tape Chronicles: Rust/C++ Interop
53mC++/Rust Interop: A Practical Guide to Bridging the Gap Between C++ and Rust
25mRust and C++
52mBuilding Bridges: C++ Interop, Foreign Function Interfaces & ABI
41mC++ Migration Strategies