It does not mean "memory safe" in general. It means different things in different contexts.
Also, I wasn't making a point about the word "safe". I was making a point that if go is "safe", then the word "safe" is useless.
There is a problem here. Don't want to call it "unsafe"? Ok. Call it crashy, instead.
I agree it's better to avoid null dereference errors by not putting null in your language, but by the normal meaning of safe here, go is safe.