On Monday, February 26, 2018 at 12:35:13 PM UTC-5, Jakob Borg wrote: > > On 26 Feb 2018, at 18:21, "di...@veryhaha.com <javascript:>" < > di...@veryhaha.com <javascript:>> wrote: > > On Monday, February 26, 2018 at 11:48:36 AM UTC-5, Jakob Borg wrote: > <#34A5B26F-AB6C-4559-A17D-D8137AC52784@kastelo.net_> > <#34A5B26F-AB6C-4559-A17D-D8137AC52784@kastelo.net_> >> >> <#34A5B26F-AB6C-4559-A17D-D8137AC52784@kastelo.net_> >> On 26 Feb 2018, at 16:38, >> <#34A5B26F-AB6C-4559-A17D-D8137AC52784@kastelo.net_>di...@veryhaha.com >> wrote: >> >> >> Will the "sync/atomic" package get broken? >> This atomic package imports unsafe. >> >> >> If changes to unsafe break sync/atomic it’s up to the Go team to fix >> sync/atomic before releasing. Much like it’s up to other package authors to >> make sure their packages work when unsafe changes, if they depend on >> package unsafe. You can depend on sync/atomic working. >> > Show Quoted Content > >> On 26 Feb 2018, at 16:38, di...@veryhaha.com wrote: >> >> >> Will the "sync/atomic" package get broken? >> This atomic package imports unsafe. >> >> >> If changes to unsafe break sync/atomic it’s up to the Go team to fix >> sync/atomic before releasing. Much like it’s up to other package authors to >> make sure their packages work when unsafe changes, if they depend on >> package unsafe. You can depend on sync/atomic working. >> > On 26 Feb 2018, at 16:38, di...@veryhaha.com wrote: >> >> >> Will the "sync/atomic" package get broken? >> This atomic package imports unsafe. >> >> >> If changes to unsafe break sync/atomic it’s up to the Go team to fix >> sync/atomic before releasing. Much like it’s up to other package authors to >> make sure their packages work when unsafe changes, if they depend on >> package unsafe. You can depend on sync/atomic working. >> > > I mean whether or not the prototypes of the pointer functions in the > atomic packages will change? > > > I think it's a safe bet that unsafe.Pointer will continue to exist. > > //jb >
But even if it exits, those pointer atomic functions will still become unusable if the unsafe mechanism is not supported any more. -- 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.
