>
How do you address the inherent unsafeness of hardware? Even "pure" functional languages are hacking around this...
By proving the hardware correct. Then if you're running proven memory safe Rust on formally verified hardware, you're guaranteed by construction that the Rust you're writing is memory safe (for the formally-specified notion of "correct" and "memory-safe" in use, which will probably issues like manufacturing problems and compiler bugs).
A Google search for [hardware formal verification] can get you started, if you're interested. There's been a good deal of work in this area.
By proving the hardware correct. Then if you're running proven memory safe Rust on formally verified hardware, you're guaranteed by construction that the Rust you're writing is memory safe (for the formally-specified notion of "correct" and "memory-safe" in use, which will probably issues like manufacturing problems and compiler bugs).
A Google search for [hardware formal verification] can get you started, if you're interested. There's been a good deal of work in this area.