Design meeting: Update on unsafe coding guidelines #362
Description
Summary
As I've been given to understand, @rcseacord, the convener of the C standards committee and the standardization lead at Woven by Toyota, is interested in learning more about the state today of how we define behavior for unsafe Rust code and what our future plans for this might entail.
This seems a good opportunity for us all to remind ourselves where we are with this.
In particular, I think it'd be good to hear, on a call, an update from @RalfJung, if he's able, about MiniRust, about RustBelt, about the other ongoing work of his team to "develop the formal foundations for the Rust programming language [including with respect to unsafe code]", and about the status of the work of Rust's Unsafe Code Guidelines.
cc @nikomatsakis @PLeVasseur @ehuss
About this issue
This issue corresponds to a lang-team design meeting proposal. It corresponds to a possible topic of discussion that may be scheduled for deeper discussion during one of our design meetings.