Yes, tags (field numbers) can be non-contiguous. Yes, hex is accepted by protoc
No, repeated fields cannot be required On 22 January 2018 at 23:08, Ashwin Kini <[email protected]> wrote: > Hi all, > > While defining messages can the *tags *be non continous? The > documentation never mentions the same > > message abc { > optional uint32 xyz = *100*; > optional uint32 def = *200*; > optional unit32 abc = *0xDEAD01*; > > } > > The documentation says it needs to be unique. Agreed. Can they be non > continous as explained in example? . Also does it take HEX values as far > as it falls in the range mentioned in the doc? > > One more question is, can repeated fields be made required? I did a lot of > digging, seems its not possible. Can anybody confirm? I understand required > should be completely avoided. > > > > > -- > 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 an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/protobuf. > For more options, visit https://groups.google.com/d/optout. > -- Regards, Marc -- 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 an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
