Russ Cox

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 The new API is in https://github.com/golang/go/issues/64811#issuecomment-1944446920.

@prattmic raises an important point. The question is whether the more general problem of backdating the language semantics is or will be an actual problem. We have made many public...

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...

Yes, @thepudds is right (as usual 😄) about the loopvars: that's not godebug-controlled.

Have all remaining concerns about this proposal been addressed? The proposal is in the top comment: https://github.com/golang/go/issues/65573#issue-2123423370.

The default= feature is very important and should not be removed. The motivating context is that you have a file that says go 1.22 toolchain go1.24.5 but you need to...

Have all remaining concerns about this proposal been addressed? The proposal is in the top comment: https://github.com/golang/go/issues/65573#issue-2123423370.

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 The proposal is in the top comment: https://github.com/golang/go/issues/65573#issue-2123423370.

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 The proposal is in the top...

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...