2 ms·
The biggest reason would be the "native" interoperability. No FFIs because while you could call it a language it's more accurately syntax sugar. Another reason
by yazaddaruvala 12y ago
The biggest reason would be the "native" interoperability. No FFIs because while you could call it a language it's more accurately syntax sugar.
Another reason with Rust at least. Rusthon can make the same memory guarantees as Rust.
Personally I wish this was done with Ruby.. But then again I'm not writing it myself, so I can't really complain.
A random last thought, it would be really something if Rust could formally prove its memory safety and then push that whole system of lifetimes and borrow checks into LLVM or a similar abstraction on top of LLVM. Because Rust as a compiler target is very interesting but it wasn't really built for that.