The exact opposite of that, of course. Also it includes avoiding use-after-free and avoiding casting to the wrong type. You might define memory safety to be t

The exact opposite of that, of course. Also it includes avoiding use-after-free and avoiding casting to the wrong type. You might define memory safety to be that if you're accessing an object then (1) that object is actually there, and (2) it's the object you think it is.