> When I read memory safe it means that it cannot happen at all, and therefore I don't have to think about that kind of stuff when I write a program. I've neve

> When I read memory safe it means that it cannot happen at all, and therefore I don't have to think about that kind of stuff when I write a program. I've never needed to use unsafe in my Rust applications, which means that my code is 100% memory safe (by Rust definition of course). I expect libraries I am using to provide safe abstractions over unsafe, if there is any there. Sure, there were bugs (including Rust stdlib), but such small scale effectively means that this problems disappeared comparing to languages that aren't safe and that means all I need to do is maybe update some dependency once a year. It's that rare, so I will call it safe and solved problem. We can move to next one (and there are many). > It'd be more honest to say: it's memory safe until: Which is what most Rust introductions I've seen will say. I don't think anyone misunderstood this part.