in reply to Guillaume Endignoux

mastodon - Link to source

Guillaume Endignoux

If I had to highlight a key take-away from @ciura_victor's C++/Rust interoperability talk, that'd be that it's much easier to call Rust from C++ than C++ from Rust, which is indeed the case in my experience. Because many C++ language features have no equivalent in Rust.

eurorust.eu/talks/rust-c-plus-… #EuroRust

Introduction slide about convergent evolution of crustaceans to acquire a crab-like body plan.
Non-exhaustive list of C++ features having no direct Rust equivalent: 4 flavors of overloading, argument-dependent lookup, default function parameters, implicit conversion, SFINAE, in-place initialization, move constructors.
Calling C++ from Rust slide. Hard due to missing language features, unsafe, lifetimes, aliasing, non-memcpy movable types, etc.
Calling Rust from C++ slide. Doable thanks to Rust's strong type system (intended semantics are clear). However, Rust ABI isn't stable, so tools need to refresh information on every (rustc?) update.

EuroRust 2025 – October 9 & 10, Paris & online

EuroRust is a 2 day conference for the European Rust community – October 9 & 10, 2025 – in Paris & online
EuroRust
#EuroRust @Victor Ciura
⇧