I am pretty sure that you will run into problems with this. On one hand passing pointers could lead to a write after a read, and on the other hand with pass by value you could get an out of date value and then stomp over another process write. I'm pretty sure the race detector will flag this. You will have to write some kind of access lock when processes need to write to it to exclude this condition.
On Saturday, 21 April 2018 06:26:08 UTC+3, Kaveh Shahbazian wrote: > > Is it safe to access slices that shares a back array concurrently? > (Assuming the length of slices will not change) > > > -- 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.
