> Memory safety is distinct from thread safety From [2] you linked > a race condition can't violate memory safety in a Rust program on its own. From golang F

> Memory safety is distinct from thread safety From [2] you linked > a race condition can't violate memory safety in a Rust program on its own. From golang FAQ on maps not being atomic: > uncontrolled map access can crash the program This may be one very narrow case (or a more common theme), but at least in this case the thread safety becomes a memory safety concern in golang.