News for hackers. Stuff that matters.
Re:A Hoare Logic for Rust by dikaiosune on Friday September 30, 2016 @11:54AM (#12613210)
I know of a few efforts to better specify Rust in addition to ticki's (OP):

* https://github.com/nikomatsakis/rust-memory-model * http://plv.mpi-sws.org/rustbelt/ * https://kha.github.io/2016/07/22/formally-verifying-rusts-bi...

The first isn't using formal methods AFAIK, the second is, and the third is as well, but I think they're targeting safe code only.

Re:A Hoare Logic for Rust by mbrubeck on Friday September 30, 2016 @12:03PM (#12613266)
There was also Patina, which formalized a subset of safe Rust's semantics, though it was done on an older (pre-1.0) version of the language:

ftp://ftp.cs.washington.edu/tr/2015/03/UW-CSE-15-03-02.pdf

Re:A Hoare Logic for Rust by weinzierl on Friday September 30, 2016 @01:49PM (#12614004)
Also the Rust compiler had Typestate analysis at one point of its development. [1]

[1] http://marijnhaverbeke.nl/talks/rustfest_2016/#4

Re:A Hoare Logic for Rust by pcwalton on Friday September 30, 2016 @04:59PM (#12615254)
Typestate is basically all subsumed by the uniqueness system. The two systems are equivalent, so in a sense Rust still has typestate.
Re:A Hoare Logic for Rust by eruquen on Saturday October 01, 2016 @05:45AM (#12617213)
Rustbelt targets unsafe and safe code. In addition, it will also deal with concurrency (incl. weak memory).

Disclaimer: I am affiliated with the project.