Duck-Tape Chronicles - Rust C++ Interop
summary
Claim: compiler, linker and ABI guarantees matter more than glue crates for real Rust–C++ interop. Notes concrete tradeoffs: current options like CXX or plain C FFI work for tiny surfaces but force lowering complex enums, strings and trait objects; the Krabby experiment prototypes richer layouts. Swift’s value witness tables and resilience model show one viable path. Rust Foundation funding, WG21 attendance and community meetings (February notes, April 23 followup) drive incremental engineering and tooling work rather than a single silver bullet.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:46Rust C++ interop expectations
- 10:21Rust C++ interop challenges
- 15:04Compiler and linker design
- 16:49C++ ABI stability limits
- 24:18ABI stability in other languages
- 33:14Swift’s stable ABI
- 40:24Resilience domains role
- 49:40Current Rust interop limits
- 55:50Future Rust C++ interop
- 1:03:26Rust Foundation interop
- 1:08:40Getting involved in interop
related talks
37mDuck-Tape Chronicles: Rust/C++ Interop
01h 02mRust/C++ Interop: Carcinization or Intelligent Design?
58mRust for The Curious C++ Developers
53mC++/Rust Interop: A Practical Guide to Bridging the Gap Between C++ and Rust
42mPanel: Rust and C++ can work together!
52mBuilding Bridges: C++ Interop, Foreign Function Interfaces & ABI
40mRust’s approach of getting things right
25mRust and C++