Yes, that is the "workaround". I mean, the lack of WeakReference makes Go
(when implementing this pattern) at the same level as C/C++, since I have
to know when I need to "delete" the resource in order to unsubscribe the
event. I will have a look at SetFinalizer though, I haven't heard of it but
I find WeakReferences when implementing observer pattern: A service
generate events and signal listeners that the event was triggered. This
usually requires the service to have a list to all of the listeners. Now,
without weak refernece it means that any temporary listener will not be
garbage c
