Repository navigation
Replies: 1 comment
|
Yes, this is desired, and would be accepted. Borrowing might still be tricky, and we should be wary about #225 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
These days, the question of a stable ABI for Rust is far from resolved, and there's been a few attempts to allow Rust code to call other Rust code, across compiler versions of flags. See stable_abi and stabby.
These bring their own model and complexities to learn and integrate into a codebase. Sometimes, projects craft their own c translation layer to achieve this ABI compatibility.
I think Diplomat (and less clearly other interop crates like UniFFI and Interoptorus) is well positioned to offer a solution to this problem.
With a Rust backend, I guess Diplomat could generate very idiomatic code to take advantage of the bridge interface, it's usage probably looking very similar to the bridge definition.
I'm wondering what's your opinions on it, if that would be an accepted contribution, and what kind of issues do you foresee coming up ?
All reactions