Re: [protobuf] extending field and message options

All fully-qualified symbols must be a unique for an invocation of protoc. In the generated code, you can refer to the generated extension (just like referring to generated messages, enums, and services), and if their fully-qualified names weren't unique, it would result in compilation errors in

Re: [protobuf] extending field and message options

I believe this is to be expected, because these top-level extensions would end up having the same name. For example in C++ they would both be called example::exOptions and so there would be a conflict there. To get around this you can either give them different names or keep the same names but

[protobuf] extending field and message options

Hi, I have my proto file like following. package example; message ExFieldOptions { map meta_data = 1; } extend google.protobuf.FieldOptions { ExFieldOptions exOptions = 4245; } extend google.protobuf.MessageOptions { ExFieldOptions exOptions = 4245; } When I