@randall77 requested issue #65957 to be considered for backport to the next 1.22 minor release.
I'm on the fence. We only backport serious issues with no workaround, which I'm not sure this qualifies. It has been a bug since 1.18 and this is the first anyone has reported it. I'm not sure what a workaround might be, though. Does introducing a use of the array type in both packages work as a workaround?
I'll open backports and we can discuss on those issues.
@gopherbot please open backport issues. This issue may warrant backporting. It causes program crashing in some very particular circumstances. (Use of
reflect.ArrayOf, and just the right use / nonuse of the corresponding language type in particular packages.)
Comment From: thanm
Discussed during the release checkin meeting. Consensus is that this is not worth back-porting.
Comment From: randall77
I'm going to reopen for reconsideration. We've received another bug report that we're pretty sure is this issue, #67608.
Comment From: randall77
The fix is quite simple and low-risk.
Comment From: prattmic
@randall77 Should this have a 1.21 backport as well?
Comment From: randall77
There's no known instance of this bug triggering in 1.21. #67608 bisected to https://go-review.googlesource.com/c/go/+/522339 which went out in 1.22. So I would say, no backport for 1.21.
Comment From: joedian
@randall77 do we still want to create the cherry pick cl for this?
Comment From: randall77
Yes, sorry, just made it at CL 593876.
Comment From: gopherbot
Change https://go.dev/cl/593876 mentions this issue: [release-branch.go1.22] cmd/compile: mark pointer to noalg type as noalg
Comment From: dmitshur
Closed by merging CL 593876 (commit ceaf26ecce663e75c4f4b476dc3c64fa58a2f0dd) to release-branch.go1.22.