Comment by SkiFire13
2 days ago
> You could even use Rust alongside Fil-C to ensure the unsafe blocks are safe.
Isn't this what MIRI already does?
2 days ago
> You could even use Rust alongside Fil-C to ensure the unsafe blocks are safe.
Isn't this what MIRI already does?
Partially yes. Fil-C goes further in creating an entire ecosystem of Fil-C compiled "legacy" libraries, meaning all the unsafe FFI your Rust code does into C is also safe, and even many linux syscalls.
Miri is meant as more of a sanitizer type tool that you use during development to catch bugs. Fil-C is a platform you compile your entire Linux distro with for use in production.
I thought you meant to use Fil-C as a kind of sanitizer too.
I don't see a point in running Rust code in Fil-C. Due to the way Fil-C works it won't be enough to check the `unsafe` statements, so you'll pay the performance tax on safe code too (onto which you already paid the borrow checker tax!)