3 ms·
> given that their requirements lined up with what Rust is good at I would say the opposite. OP stress on the C/C++ interoperability. In rust, you need to ei
by j16sdiz 4y ago
> given that their requirements lined up with what Rust is good at
I would say the opposite.
OP stress on the C/C++ interoperability. In rust, you need to either
(1) wrap the API in something Rust-like / Borrowchecker-friendly - which need lots of planning ; or
(2) Do it with lots of unsafe code - which make the memory safety lots more complicated to reason about
For memory safety, you can get it from any GC language without extra mental load.
- Cyph0n 4y ago(1) is a one-time investment and allows you to take advantage of compiler guarantees. (2) is what every other language does for FFI anyways. In Rust, you could have a lightweight wrapper around the C API, but you would lose out on some benefits. OP said performance was critical, so why would they use a GC language?