Rust for Safe and Scalable Automotive: Insights from
summary
Rust eliminates many classic C pitfalls: a hand-conversion of C safety lint checks into idiomatic Rust shows 62% compile-time mitigated, ~25% mitigated at runtime and about 10% not mitigated (four cases need extra crates, six require further tooling). Eclipse SDV projects show ~37% Rust share. The Eclipse Trustable Software Framework codifies six tenets and 16 assertions into a graph of evidence, with tooling like TrueDag and a Rust safety monitor built to demonstrate a Linux-based safety chain without a hypervisor.
AI-written summary · about
chapters (6)
- 0:00Eclipse Foundation and Rust
- 15:19Rust in automotive open source
- 25:14Trustable Software Framework overview
- 31:53Trustable Software Framework in practice
- 46:40Governance costs and collaboration
- 55:41Q&A
related talks
07mLightning Talk: “How Rust Is Steering Automotive Software Toward Safety”
56mRust for Foundation Software
25mContinuous compliance with Rust in automotive software
22mRust as a Foundation for a Safe and Sustainable Future
40mWhat's up with Rust?
45mRust
40mWhy Rust?
45mBuilding Safe and Secure Systems in Rust