Post

How often do people run into the SetFinalizer footguns in Go? (Accidental cycle, for example.) Would a GODEBUG that does something slow but tells you when you've made a mistake be useful to you? (Maybe even just for tests, to prevent a regression?) Sketch: go-review.googlesource.com/c/go/+/634599

So would this replace the desire for a GODEBUG to disable the tiny allocator to help troubleshoot a finalizer/cleanup issue (because this would flag a finalizer or cleanup that isn’t firing because of the tiny allocator)? Would this CL also help for weak pointer tiny allocator related issues?