Allow to embed Rust in native sources #2351
Conversation
|
We were discussing this PR in Discord today. @ekrich mentioned that it was in good shape but there wasn't much interest. So I wanted to make sure to express my interest 😁 The appeal of this would be to help integrate/bind with Tokio which is the modern answer to libuv (e.g., Node.js uses libuv but Deno uses Tokio). Specifically, the goal would be to use Tokio to provide a Native implementation of the cross-platform fs2 I/O APIs, which already support both JVM and Node.js. Cross-building these APIs almost immediately unlocks other popular libs such as http4s and skunk which are pure-crosses built on top of fs2. Thanks for pursuing these initiatives! |
|
@WojciechMazur This PR is exciting :) What is the status on this? |
| let str: &str = c_str.to_str().unwrap(); | ||
| return str == "Hello Rust"; | ||
| } | ||
| } |
| #[no_mangle] | ||
| pub extern "C" fn isEven(x: i32) -> bool { | ||
| x % 2 == 0 | ||
| } |
|
I'm working on refreshing this PR in #2566. |
After sugestion of @ekrich and some discussion with Scala tooling team in @VirtusLab we've come up with implementation allowing to embed Rust sources in native sources of SN durring our last hacking session.
Current solution supports both compilation of simple programs using
rustcas well as more complicated projects using external dependencies using crates.io. It would allow for bootsrapping frameworks calling Rust from Scala Native. Some additional abstractions might be needed to introduce in order to fullfill Rusts memory management contract - especially read-only references, as well as to provide bindings for rust allowing to allocate memory inside Scala Native's GC, most of that might be possible to introduce as third-party library.It's worth to note that compilation of Rust sources currently always creates static libraries instead of object files, this solution has it's drawbacks - especially larger size of created artifacts, however it allows us to use Rust's std library, which might be problematic to provide on it's own. Due to this decision we needed to introduce some additional types, that would keep track either given source is object file or static library.