Dave Cheney

I had this problem with a version of my profile package. My solution was to move the code into a branch and deleting all the code from the package on...

What about an init function which prints a message when any program links against it. On Fri, 2 Dec 2016, 17:51 Juliusz Chroboczek wrote: > FWIW, the message in this...

I don't see how this could be implemented safely. Other Go code could have references to functions and symbols loaded from the plugin-would unloading the plugin make those dangling references,...

> Would it be possible to make close fail until the reference count of all symbols in the plugin reached 1, so that the plugin itself was the only structure...

Your proposal is to add a way to free resources associated with a plugin. If this is delegated to a finaliser it becomes non deterministic when this freeing occurs as...

How can you close a goroutine? The runtime doesn't give you any way to get a handle or an identifier for a goroutine? On Tue, 23 May 2017, 09:54 Zac...

Yup, a goroutine dies/quits/goes away when the function that was passed to the go statement returns. So that leaves the problem of ensuring every goroutine that may have access to...

That's a finaliser. On Sun, 4 Jun 2017, 11:45 Demi Marie Obenour wrote: > What about having the GC close any plugins that are no longer referenced? > > —...

It feels like somewhere between rusts ownership system and a finaliser. On Sun, 4 Jun 2017, 13:48 Zac Pullar-Strecker wrote: > @davecheney Any comment on making it a > compile-time...

@DemiMarie this approach is problematic, please see my comments about finalisers earlier in this thread.