> GMM violation = UB This is definitionally correct (shrug) > Dilettante programmers certainly do not know [that] Go slices, strings, and interface values are

> GMM violation = UB This is definitionally correct (shrug) > Dilettante programmers certainly do not know [that] Go slices, strings, and interface values are unsafely non-atomic. Yes. They do. As soon as a Go programmer learns that there is such a thing as concurrency and "thread safety" they learn that nothing in Go is "thread safe" by default. > Go is not memory-safe. "Memory-safe" is not a precisely defined concept. Go is memory safe by some definitions, not by others.