On Thu, Feb 9, 2017 at 1:26 AM, <kpr...@atlassian.com> wrote: > The feature I want most in go is automatic reference counting. I don't > really care how mainline GC works but I want the language to be open to the > possibility of ARC-GC. In order for that to be able to handle cycles you > need a weak_ptr type that can requires explicit graduation to a shared_ptr. > > What would it mean to add the weak keyword to standard go? As best I can > reason it would serve as ownership documentation under trace based and > little more so it wouldn't be harmful. At small run time cost you could > with a flag force non-nil values for all implicitly strong / shared pointers > which could aid in debugging. Is it a hopeless dream to think this could get > added one day?
Previous discussion here: https://groups.google.com/forum/#!topic/golang-nuts/PYWxjT2v6ps As I mentioned back then, I do not think it would be appropriate to add them to the language. One of the indirect consequences of that previous discussion was sync.Pool, which is a specific form of weak reference. 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.
