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

go-review.googlesource.comgo-review.googlesource.comGerrit Code Review

Michael Knyszek

@michael.express

If such a debugging mode would be useful, what would be the most helpful information for debugging? Stack trace where the finalizer was applied? The object's type?

24/12/24, 8:53 pm0 reposts0 likes

No replies yet.