As long as we’re running arbitrary binaries with security in mind, we may as well implement our libc in Rust. This reduces the risk of buffer overflow escapes from our sandbox.
Fortunately, Rust is able to output C-compatible object files. So while cloudlibc could be reimplemented in Rust, there is no technical requirement that user applications be written in Rust; they can continue using a typical C FFI.
I think this should be done with cloudlibc proper, as well as the cloudabi runtime and any dependencies as well, such as the yaml arg parser.
As long as we’re running arbitrary binaries with security in mind, we may as well implement our libc in Rust. This reduces the risk of buffer overflow escapes from our sandbox.
Fortunately, Rust is able to output C-compatible object files. So while cloudlibc could be reimplemented in Rust, there is no technical requirement that user applications be written in Rust; they can continue using a typical C FFI.
I think this should be done with cloudlibc proper, as well as the cloudabi runtime and any dependencies as well, such as the yaml arg parser.