>> I think it only catches concurrent access to the same address, so not sure >> if it catches everything. > > > If two things aren't writing concurrently to the same address, what's the > problem?
I took that to mean 'things may be updating concurrently at different addresses inside an array backing the same slice'. But the race detector will flag as soon as a read is attempted by another goroutine on any of those. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAK4xykU5nKhU0BFocR0XP-mYD0rY246Hu6Aq9AG95t-Dh7n-PA%40mail.gmail.com.
