Sean Liao
would this be the same as #44026 ?
this sounds very specialized does it have wide usage elsewhere? https://go.dev/doc/faq#x_in_std
I did, but minor version info is already available (the `-u` and `-versions` flag for `go list`). What's new and hard is obtaining information about major versions.
I think TraceID / SpanID should instead be implementing the more generic [encoding.TextMarshaler](https://pkg.go.dev/encoding#TextMarshaler) / [encoding.TextUnmarshaler](https://pkg.go.dev/encoding#TextUnmarshaler) interfaces which encoding/json supports.
`go env` has a read only env `GOVERSION=`. perhaps `go env` should get a new env `GOLOCALVERSION`, and `go version` get a second line prefixes with `local: ` ?
This is a dupe of #36503 (it's long, but the final focus was on merging cancelation), where the final decision was: > We can decline this for now and then...
What we want to see is the need for it within the Go ecosystem, not a different language which will have different patterns available to it.
There doesn't appear to be any significant new evidence compared to then this was proposed last year.
Duplicate of ##36503
Right now this issue isn't very actionable with the lack of information: what were the exact steps you took to generate the profile? what does blank mean? do you have...