Comment Comment by pjmlp Interestingly enough, by following up some references of the article I discovered that Go is also following up on Java and .NET design decisions, that maybe could be there early on.- Deprecating finalizers and using cleaner queues (https://openjdk.org/jeps/421)- Weak references (https://learn.microsoft.com/en-us/dotnet/api/system.weakrefe..., https://docs.oracle.com/javase/8/docs/api/java/lang/ref/Weak...)Related tickets,"runtime: add AddCleanup and deprecate SetFinalizer" - https://github.com/golang/go/issues/67535"weak: new package providing weak pointers" - https://github.com/golang/go/issues/67552One day Go will eventually have all those features that they deemed unnecessary from "complex" languages. parent pjmlp 2 years ago
- Deprecating finalizers and using cleaner queues (https://openjdk.org/jeps/421)
- Weak references (https://learn.microsoft.com/en-us/dotnet/api/system.weakrefe..., https://docs.oracle.com/javase/8/docs/api/java/lang/ref/Weak...)
Related tickets,
"runtime: add AddCleanup and deprecate SetFinalizer" - https://github.com/golang/go/issues/67535
"weak: new package providing weak pointers" - https://github.com/golang/go/issues/67552
One day Go will eventually have all those features that they deemed unnecessary from "complex" languages.