Russ Cox

Would it make sense to add a field to the Challenge type instead of having a whole new method?

OK, so it sounds like maybe adding // Payload is the JSON-formatted payload that the client sends // to the server to indicate it is ready to respond to the...

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

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 https://github.com/golang/go/issues/69095#issue-2490518612.

When b.Loop inlines, `for b.Loop() { ... }` has almost no overhead while enabling multiple trials and any number of other interesting measurements. I really like it a lot. It's...

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 only real question about this was the auto-Keep. All the other benefits listed in the top comment are clear wins. Given that Keep is now likely accept, it seems...

Note that the current proposal is used as `for b.Loop() { ... }` - there is no callback anymore.

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

b.Loop has real benefits separate from Keep, so it's worth doing even if we still have questions about Keep. So this seems like it can move to accept.