Discussion
Loading...

Post

Log in
  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Guillaume Endignoux
Guillaume Endignoux
@gendx@infosec.exchange  ·  activity timestamp 4 months ago

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.

https://eurorust.eu/talks/rust-c-plus-plus-interop/ #EuroRust

4 media
Introduction slide about convergent evolution of crustaceans to acquire a crab-like body plan.
Introduction slide about convergent evolution of crustaceans to acquire a crab-like body plan.
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.
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.
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 C++ from Rust slide. Hard due to missing language features, unsafe, lifetimes, aliasing, non-memcpy movable types, etc.
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.
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.
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.
  • Copy link
  • Flag this post
  • Block

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.2-alpha.7 no JS en
Automatic federation enabled
Log in
  • Explore
  • About
  • Members
  • Code of Conduct