David Chase
David Chase
Loong64 isn't supported by 1.18, so not a bug.
The three bugs/CLs were collapsed into one, and this is the one. Therefore it is the backport, though loong64 code won't be included in the 1.18 backport CL.
Hi, I'll get it this time (and sorry for the late reply; I was traveling, then the weekend.) Thank you for checking, though.
CC @golang/vulndb
But note https://github.com/golang/go/issues/57263#issuecomment-1350339728
CC @golang/release
But note https://github.com/golang/go/issues/57263#issuecomment-1350339728
@ianlancetaylor @aclements I can imagine this going wrong in interesting ways, not sure if we can support it. [MS VEH article](https://docs.microsoft.com/en-us/windows/win32/debug/vectored-exception-handling)
@griesemer Reading "Composite types in constraints" in https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md I get the impression that this ought to work; the example there says "this doesn't work because the field types for X...
Skimming this, I didn't see mention/proposal of the possibility of enforcing this dynamically, and I think we can do that for #cgo nocallback. If that sets a bit in the...