Nothing in GP's comment ever even suggests that the Go compiler would insert telemetry into binaries. It's good practice not to put words in people's mouths.
Perhaps, it may have been a bit of a stretch on my end, but not unfounded given ...
> Repositories for binary packages could compile their versions with telemetry disabled.
... the overall tone of the comment, and peer comments that seem to believe that this is the case. Only GP can confirm their belief to where telemetry would be implemented.
One does not have to "compile with telemetry disabled" but rather disable telemetry with an ENV VAR. It is the "compile" part which has me believe GP believes that this is embedding telemetry in binaries built with Go, which is not what is happening at all.
A runtime option for disabling telemetry has little value for build tools because any random build script can re-enable it without you knowing. Even more so if it's an environment variable for opting out, because it's so common for build scripts to clear environment variables for legitimate reasons.
Whether there's a compile time option to disable telemetry altogether is what many downstream packagers would probably be interested in.
