In support of the parent who already knows all this: you don't even need to take raw pointers to have these problems! You'll usually get a slice from your alloc

In support of the parent who already knows all this: you don't even need to take raw pointers to have these problems! You'll usually get a slice from your allocator. Keeping any copy of that or any slice into that (e.g. a string in a struct obtained by deserializing a json document into a short-lived slab of memory) will get you use-after-frees too.