-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/playground: "// GOEXPERIMENT=xxx“ line often causes "timeout running go build” #61985
Comments
Seeing this too. Does opting into the experiment need rebuilding parts of the stdlib, such as fmt? |
(attn @findleyr @golang/release) |
This is probably due to recompilation of std archives (which are cached following https://go.dev/cl/460635). Perhaps we should add a special case and build archives with @bcmills can you confirm whether adding a second build of CC @rsc, who added support for |
Yes, adding That said, I question whether the benefit of doing so would be worth the cost, given the need to deploy and maintain it. I hope that the revised loop variable semantics will soon be available without setting |
It is already available if you select "Go dev branch" on the playground (since fe1daf2) |
With 1.22 out, this seems to be even worse with |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What did you do?
https://go.dev/play/p/VwcNVnozJlu
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: