Federation Bot @Federation_Bot · activity timestamp 4 months ago A few technical examples of when C++/Rust interop is complicated. #EuroRust Read more Read less Translate 4 media alt Function overloading: Rust shouldn't be made more complicated for the sake of interop. Function overloading: Rust shouldn't be made more complicated for the sake of interop. alt C++ tail padding (child class can be put at the tail of a base class). C++ tail padding (child class can be put at the tail of a base class). alt C++ assumes all values are non-relocatable, which hurts everybody for the benefit of a few questionable designs. C++ assumes all values are non-relocatable, which hurts everybody for the benefit of a few questionable designs. alt C++26 will have a concept of trivial relocatability. C++26 will have a concept of trivial relocatability. Reply Boost or quote Boost Quote pending approval Like More actions Copy link Flag this post Block
alt Function overloading: Rust shouldn't be made more complicated for the sake of interop. Function overloading: Rust shouldn't be made more complicated for the sake of interop.
alt C++ tail padding (child class can be put at the tail of a base class). C++ tail padding (child class can be put at the tail of a base class).
alt C++ assumes all values are non-relocatable, which hurts everybody for the benefit of a few questionable designs. C++ assumes all values are non-relocatable, which hurts everybody for the benefit of a few questionable designs.
alt C++26 will have a concept of trivial relocatability. C++26 will have a concept of trivial relocatability.
