Rust is (Un)safe: Writing Safety-Critical Coding Guidelines

By Pete LeVasseur

Talk - Wednesday, 16 September
11:15

Rust has earned its reputation for improving memory-, type-, and thread-safety in systems software. But what happens when you use it in safety-critical settings? What about brown-field projects with lots of existing code in other languages? Or code that interacts with hardware, outside the purview of Rust’s Abstract Machine? In this talk we cover the gaps between Safe Rust and Unsafe Rust and the need for Safety-Critical Rust Coding Guidelines like those being developed by the Safety-Critical Rust Consortium.

Speaker

speaker.name

Pete LeVasseur

Pete LeVasseur guides Rust adoption efforts at Woven by Toyota and its suitability for the highest levels of safety-criticality. He’s also lead of the Safety-Critical Rust Consortium, which has a broad base of support for making Rust a suitable first-language choice for safety-critical domains such as Automotive, Aerospace, and Industrial. Pete’s also an Eclipse SDV WG Ambassador and hosts the bi-weekly Rust Special Interest Group, where those interested in Rust in Automotive and safety-critical domains more generally can share and learn. Pete is also involved with Rust Project activities, such as co-leading the Content Team and being a member of the Rust Vision Doc Team; he loves interviewing those doing interesting things with Rust.