On Thu, Feb 9, 2017 at 4:46 PM, <kpr...@atlassian.com> wrote: > > I'll look into that api and maybe it will solve my problems. Though, to be > understood I'm not asking for ARC, I'm asking for a keyword so the spec is > compatible with ARC.
But you don't need a keyword to get weak pointers. Given the existence of concurrent GC, the only safe way to use a weak pointer for anything whatsoever is to call a runtime function that examines the weak pointer and returns nil if the object is gone or a strong pointer to the object if it is not. That strong pointer will then keep the object alive until you discard it. Since you have to call a runtime function anyhow, putting weak pointers into the language itself is not necessary. They can be implemented as an opaque type in the runtime package. 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.
