|
|
|
|
|
|
by zozbot234
324 days ago
|
|
|
> Now a race condition between one thread writing and another thread reading or writing a variable is a memory safety issue. No it isn't, because the torn write cannot have arbitrary effects that potentially break the program. It only becomes such if you rely on such a variable to establish an invariant about memory that's broken if a torn write occurs (such as by encoding a ptr+len in it), which is just silly. Don't do that! |
|
|
tell that to the Go runtime, which relies on slices always being valid and not being able to create invalid ones.