> > From the GC POV, the only interesting thing about an unsafe.Pointer is if > its value falls anywhere into a GC managed memory block for liveness > analysis, AFAIK. > And then it will check that memory block for stuff that looks like a pointer (not caring what the actual type being pointed to is) afaik. That is what I meant with conservative GC. I found a thread from 2013, where Ian says the same https://groups.google.com/forum/#!topic/golang-nuts/yNis7bQG_rY. Maybe my information is outdated, I haven't followed the GC evolution in recent years that closely.
-- 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. For more options, visit https://groups.google.com/d/optout.
