Re:RustBelt: Logical Foundations for the Future of Safe Syst...
by GolDDranks on Saturday January 09, 2016 @12:04PM
(#10871934)
What do you mean? Do you mean that hardware is unreliable or might break and thus even a sound program, or a program that doesn't do anything that counts as unspecified behaviour, is not 100% safe? Or that with "unsafe" escape hatches often needed to directly interop with hardware are a problem?
[ Parent
| on HN ]
Re:RustBelt: Logical Foundations for the Future of Safe Syst...
by GolDDranks on Saturday January 09, 2016 @12:08PM
(#10871948)
If it's the former, I agree.
If it's the latter, well, in Rust, the norm is to design safe abstractions around unsafe code. For example the vector class of the Rust standard library contains some unsafe code, but with the all parts that are unsafe being private, the public API exposed is essentially safe.
If this project comes up with reasonable semantics what can be considered to be "safe" with unsafe code, we can verify, that the unsafe bits of the standard library (and other libraries) are being used in a safe manner.