lfolger

Oops I thought it was the public documentation. Sorry about that. I expect this to reach the public docs eventually. I'll keep the posted snippet for now but removed the...

FYI: the documentation is now available publicly: https://protobuf.dev/editions/implementation/

I filed https://github.com/protocolbuffers/protobuf/issues/17099 as a first step to get clarity on this. I'm not even sure if we can change the Go behavior if we wanted to because it would...

We still end up with the problem that the output generated by Go cannot be parsed by the other languages. But I agree that extending the unmarshalling makes it more...

I only tested it with C++, but C++ doesn't accept: `{"@type":"type.googleapis.com/google.protobuf.Empty","value":{}}` It fails with ``` invalid JSON in google.protobuf.Any @ : message google.protobuf.Empty, near 1:62 (offset 61): no such field:...

Given the inconsistencies and the fact that Java/C++ don't accept the currently documented formatting, would it be reasonable to make all parsers accept both formattings? C++ seems to fail if...

One advantage the `proto.Int32` function has it always makes a copy of the underlying value. Users are naturally guided towards using these functions when populating their protos. If we don't...