thepudds

As proposed, is it correct that this would not directly help with #66653? (I lost the thread of this discussion a bit... I looked over it again to try to...

> I think it helps for https://github.com/golang/go/issues/66653 if you downloaded the source repo pointed to by pkgsite and ran go mod verify -tag to check that it matched what pkgsite...

Hi @mknyszek, I'm curious what you think about possibly backporting to the go1.25 release branch the change I made in https://go.dev/cl/694376 (the wording change for the panic message)? E.g., maybe...

Hi @odeke-em, thanks for checking. The first CL was merged, and the second CL I think can wait until 1.27. I just updated the milestone.

Hi @aclements and @dr2chase thanks for the feedback! > And yes for printing it is also necessary to tackle reflection FWIW, this issue here I think might be 1 of...

FWIW, as part of working on this, I wanted to see if it would be reasonable to expand some of the ways escape analysis is tested in the hopes of...

Hi @mdempsky, FYI, I have recently returned to this, including trying to get final +1s and whatnot for some of my related CLs that had been ready for a while...

Possibly related to #72887 (or maybe not). It seems to reproduce with tip on the playground: https://go.dev/play/p/AzuM0eY_vGH?v=gotip @adamlouis, what do you get if you add `-gcflags=-h` flag to `go run`...

@adamlouis, also, I should add -- thanks for filing this, and especially thanks for including a nice minimal reproducer, which should be enough for others to investigate further (and no...