tors 8 sep. 2016 kl 12:46 skrev T L <tapir....@gmail.com>: > > On Thursday, September 8, 2016 at 12:33:37 AM UTC+8, Ian Lance Taylor > wrote: > >> Perhaps you could explain what kind of compatibility risk you are >> concerned about that is not covered by the Go 1 compatibility >> guarantee. Please give an example of code that will work today but >> that you think may stop working in future releases. Thanks. >> > > As the go1compat <https://golang.org/doc/go1compat> says unsafe package > is not promised to keep compatibility, > so I think atomic.Load/Store/SwapPointer functions are also not promised > to keep compatibility, am I right? >
But package sync/atomic is not package unsafe, so why would you think that? //jb -- 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.
