On Thu, Jun 13, 2019 at 8:52 AM <tgptial...@gmail.com> wrote: > > 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 > collected and thus we will have memory grow without limits, since the > listeners will not be collected as they are referenced by the service. When > it comes to this, WeakReferences are mandatory and unfortunately Go doesn't > support them :'(
Go has finalizers (https://golang.org/pkg/runtime/#SetFinalizer). A finalizer on a handle object can be used to implement what you describe. Ian > terça-feira, 5 de Março de 2013 às 23:13:05 UTC, Steve McCoy escreveu: >> >> >> >> On Tuesday, March 5, 2013 5:43:35 PM UTC-5, Jan Mercl wrote: >>> >>> On Tue, Mar 5, 2013 at 11:24 PM, Dustin Sallings <dsal...@gmail.com> wrote: >>> > Strong reference: "hands off, gc" >>> > Weak reference: "0 this if no strong reference exists" >>> > Soft refernce: "0 this if no strong reference exists and we're low >>> > on RAM" >>> >>> This is magic, even though feasible by the runtime. Go excels in >>> explicitness, even though that may mean more user coding. My feeling >>> is that those two approaches don't mix well, to put it mildly. >>> >>> -j >> >> >> It's not magic; it's not as though people won't know they have an instance >> of a weak reference on their hands. >> >> Anyhow, I don't care if Go ever gets them, but there are other fun things >> that can be done with weak references that don't have anything to do with >> caches. I wrote a Java tool+package that keeps track of every object created >> while the program runs and asserts some preconditions whenever an object is >> accessed. Of course, memory would be extremely wasted if I kept them all in >> a map with strong references for the keys, so I instead used a WeakHashMap, >> allowing the garbage collector to clean things up in a typical fashion. >> Using explicit reference counting would've been painful for that. > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/19d2f189-4dc6-406b-bd1e-45c1deeef054%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcV5fmQYTY3MjjRjtKhS5Qxit_jok%2Bp%2Bxs%2BpSTQaEeGThw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
