Austin Clements
Austin Clements
In https://github.com/golang/go/issues/61515#issuecomment-1646206378, we were thinking "we would implicitly apply Keep to every function argument and result in the closure passed directly to Loop." That was when we were thinking of...
The reason for applying it to function arguments is to prevent unintended constant-folding *into* a function being benchmarked. There's discussion about this on #61179 if you search for "constant" (there...
Just to make sure I understand, I see that most of this API is in 1.24, but the issue is still open. Is it just Transport.StrictMaxConcurrentRequests that's missing from 1.24?
> If you'd like, I can close this issue and open a new one for StrictMaxConcurrentRequests. No need. Thanks for the update!
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. — aclements for the proposal review...
Could someone post the API that's being proposed? Thanks.
@gopherbot , please open a backport to 1.23.
Just a thought: 3560cf0afb3c29300a6c88ccd98256949ca7a6f6 was to deal with an OS thread's stack potentially moving between calls, which is a fairly obscure condition. If we discover the stack has moved, could...
Is there ever a reason a tool using gcexportdata would need to read old export data? I can't think of any, but want to put the question out there.
Thanks for playing devil's advocate everyone. :) I think we can move this forward.