Re:Compiling C to Safe Rust, Formalized
by oconnor663 on Saturday December 21, 2024 @02:02AM
(#42477984)
More important than whether you use a little unsafe or a lot, is whether you can find a clean boundary above which everything can be safe. Something like a hash function or a block cipher can be piles and piles of assembly under the covers, but since the API is bytes-in-bytes-out, the safety concerns are minimal. On the other hand, memory-mapping a file is just one FFI function call, but the uncontrollable mutability of the whole thing tends to poison everything above it with unsafety.
[ Parent
| on HN ]
There are no comments on this comment yet.