I just glanced over it but if this does what it seems to do it is really a great piece of work.
One of the biggest problems with typical FFIs is that they not only use the C-ABI but also at some point invoke some C-API so that the type safety features that both involved languages have, but C does not have, are normally lost at the boundary.
Generating the C bindings from a description of the Rust and C++ interface is a really neat idea.
Now can this be used inside a standard C++ project? Could we write pieces of code in Rust to gradually augment a C++ library?
One of the biggest problems with typical FFIs is that they not only use the C-ABI but also at some point invoke some C-API so that the type safety features that both involved languages have, but C does not have, are normally lost at the boundary.
Generating the C bindings from a description of the Rust and C++ interface is a really neat idea.
Now can this be used inside a standard C++ project? Could we write pieces of code in Rust to gradually augment a C++ library?