Joe Tsai

Is there an error message you are getting? IIRC, you can do something like: `GODEBUG=cmdgo=2 go get $PACKAGE` to print more output.

This is a known problem. It is related to but not quite identical to #33993 and #22967. Fundamentally, the issue is that the "encoding/json" package has an non-addressable value on...

Unfortunately not, I used to manage the deployment of the latest Go release into Google's codebase and it was my job to understand why various tests would fail. Most times...

> I believe it's impossible to fix a bug and keep the bug unfixed at the same time. Agreed and highly unfortunate. I made the [argument earlier](https://github.com/golang/go/issues/68919#issuecomment-2294635147): > I agree...

> Doing this way can take many years. This is the reality of using a programming language that has arguably ["crossed the chasm"](https://youtu.be/pLvZRnK2WRE?feature=shared&t=292). Prior to crossing the chasm, we can...

Also, I think much of the discussion has been re-hashing the same arguments. Fundamentally, I think we have different perspectives on which take higher priority: fixing a bug or providing...

I proposed golang/go#70547 which would address this in a more ecosystem-wide manner since invalid UTF-8 is not unique to protobuf, but many formats and protocols.

Hi, thanks for the contribution. It's a known issue that the reporter does not print enough context for all use cases and this is something worth addressing, but I believe...

I'm not fond of introducing any build tags to separate behavior. But I'm more sympathetic to a clean refactor that makes it such that use of `Equal`-only can exercise more...