Russ Cox
There are at least three different things people might want here (and have asked for either here or other places): - Build all binaries and don't save them. - Build...
Stopped.
This proposal has been added to the [active column](https://go.dev/s/proposal-status#active) of the proposals project and will now be reviewed at the weekly proposal review meetings. — rsc for the proposal review...
The annotations in the C comment today begin with `#cgo`, and we can't easily match it to the "upcoming" C function since we don't parse the C code. Perhaps: #cgo...
Updated title. Sounds like #cgo noescape and #cgo nocallback are okay. Have all concerns about this proposal been addressed?
Yes, we should check nocallback dynamically - very easy.
Based on the discussion above, this proposal seems like a **[likely accept](https://go.dev/s/proposal-status#likely-accept)**. — rsc for the proposal review group
No change in consensus, so **[accepted](https://go.dev/s/proposal-status#accepted)**. 🎉 This issue now tracks the work of implementing the proposal. — rsc for the proposal review group
It turns out that for compatibility reasons we cannot release this feature until Go 1.23. We will land the appropriate preparatory work in Go 1.22 and then enable it in...
Also any rollback of my rollback for Go 1.23 should chase down why using #cgo noescape causes crashes, as in #63739.