Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Modelling Rust's unsafe code seems pretty hard to me as afaik there are no formal semantics for Rust.


In that case, one could just go with the semantics of the SPARK-like tool with equivalent algorithm, turn that to C or assembly, and use it with Rust's FFI. That's similar to my proposal for Rust + x86 Proved or TALC. This is also an area where formal specifications can have benefit showing intent for unsafe Rust and the proven replacement.


I guess people will try anyway : https://kha.github.io/2016/07/22/formally-verifying-rusts-bi... There's some great work on this front coming from the Rustbelt lab : https://www.mpi-sws.org/~dreyer/papers/rustbelt/paper.pdf and http://plv.mpi-sws.org/rustbelt/




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: