-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: go env
does not show GODEBUG
#65777
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Change https://go.dev/cl/565095 mentions this issue: |
I think this was an oversight from #56986, which made |
Change https://go.dev/cl/566097 mentions this issue: |
It seems like go env should support printing GODEBUG, since it is relevant to debugging problems with go generally. But since GODEBUG is a runtime setting, not a build-time setting, go env -w GODEBUG=foo should not work, since it would be writing the setting into a file the runtime does not read. (Nor should every Go program read that file on startup.) |
That makes sense to me. Thanks for the fix! |
Go version
go version devel go1.23-86a32d6d9c 2024-02-17 06:03:15 +0000 linux/amd64
Output of
go env
in your module/workspace:What did you do?
Set GODEBUG and expect
go env
orgo env GODEBUG
to show me. Particularly now that its value can change the behavior of the standard library, e.g.GODEBUG=gotypesalias=1
.What did you see happen?
What did you expect to see?
The text was updated successfully, but these errors were encountered: