Ferrocene: Road to Rust in mission and safety-critical software development

Ferrocene Part 1 - The Pitch

https://ferrous-systems.com/blog/sealed-rust-the-pitch/

Ferrocene Part 2 - The Plan

https://ferrous-systems.com/blog/sealed-rust-the-plan/

"Critical Section Rust Q&A: Embedded World 2021"

https://youtu.be/C3X-H4w5a7Q

That would be an excellent idea.

A Rust subset which would be type safe, memory safe and maybe even concurrency safe, but I doubt that the third is possible. Type safety would be easy, just omit unsafe blocks.

Memory safety is being worked on for a decade, with still 75% stack overflow issues unresolved. So very advanced. But an early rust was memory-safe, so just re-add the GC. And then you have the unsafe stdlib, which would also need at least a year to fix. But without IO (embedded) doable