I'm familiar with (and greatly appreciate!) the guarantees regarding overflow for ordinary integer arithmetic in the Go spec, but I've been unable to locate anything that reassures me that similar guarantees apply for the sync/atomic.Add* functions. Is there any official statement anywhere on this subject?
Empirically, with the gc toolchain (1.7.1) on x86-64, things seem to work as expected for all of int32/int64/uint32/uint64, but I don't feel safe assuming that categorically. Thanks, -NK -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
