On Thursday, September 8, 2016 at 12:33:37 AM UTC+8, Ian Lance Taylor wrote: > > On Wed, Sep 7, 2016 at 8:16 AM, T L <tapi...@gmail.com <javascript:>> > wrote: > > > > On Wednesday, September 7, 2016 at 10:56:38 PM UTC+8, Jan Mercl wrote: > >> > >> On Wed, Sep 7, 2016 at 4:54 PM T L <tapi...@gmail.com> wrote: > >> > >> https://golang.org/doc/go1compat > >> > > > > Then how to write compatibility safe atomic pointer reads/writes code? > Do I > > must use atomic.Value for pointers? > > 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? > > Ian > -- 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.
