But it returns the new slice. On Thursday, January 19, 2017 at 2:40:30 PM UTC-8, freeformz wrote: > > No, it is not.* > > * appending can replace the underlying array, so in certain situations it > can be, but that's more by accident IMO so just don't rely on that. > > On Thu, Jan 19, 2017 at 1:43 PM xiaohai dai <[email protected] > <javascript:>> wrote: > >> I know that map in golang is not thread-safe for writing. >> However, I'm not sure slice/array is thread-safe for writing. I have >> searched the related posts and blogs in google, but find no unambiguous >> statement. >> >> Thanks in advance! >> >> -- >> 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 [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> >
-- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
