Re: [protobuf] Are protobufs serialised canonically?

Formally: no. Practically: almost always You shouldn't **demand** it. Basically, it goes like this: - the spec asks that writers *should* write fields in order - the spec asks that readers *must* allow fields in any order - data can be concatenated as a merge, meaning fields can appear out of

Re: [protobuf] Are protobufs serialised canonically?

I guess I just replied to that thread. On Tue, Jul 25, 2017 at 1:26 PM wrote: > (Attempt 2 - I'm not sure if messages to this list and moderated or > whether my first one just got lost in the ether) > > Are protobufs serialised canonically? By that I mean is the same

[protobuf] Are protobufs serialised canonically?

(Attempt 2 - I'm not sure if messages to this list and moderated or whether my first one just got lost in the ether) Are protobufs serialised canonically? By that I mean is the same message with the same fields populated with the same data guaranteed to serialise to the same sequence of

[protobuf] CodedInputStream

The documentation of CodedInputStream doesn't match the updates making the class abstract. Documentation needs updated. -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send