> runtime validation around pointers and array lookups and things. I think you're right but "validation around pointers and array lookups" makes it sound far b

> runtime validation around pointers and array lookups and things. I think you're right but "validation around pointers and array lookups" makes it sound far better than it is. That sounds like the sort of strong validation is "safe" Rust gives you. But all it does is ensure the WASM virtual machine "executing" the WASM code doesn't access RAM outside of the VM's memory space. Everything in that memory space is fair game, so all the foot shooting stuff C allows like corrupting pointers and following them within that memory space is still possible. It achieves what they want for security I guess, but not much more.