Re:The absurd cost of finalizers in Go
by selimthegrim on Saturday May 20, 2023 @03:39PM
(#36014915)
This is the post: https://crawshaw.io/blog/sharp-edged-finalizers
[ Parent
| on HN ]
Thanks. So, the small useful feature is that it can be used to (unreliably, as finalizers aren’t guaranteed to run) detect resource leaks.
Such code wouldn’t have to mutate the object being finalized (or any other object, for that matter), so I think that use case would better be served by a more light-weight feature, removing finalizers edge cases such as objects that get revived.