Thanks Josh, we don't use default values, we don't use extensions and we
don't use accessor methods. All our messages (C++) are using very simple
native fields and embedded without messages or messages imported from other
packages. You comments encouraged me even more to upgrade the v3.
You can use the latest version but still use a corpus files syntax="proto2"
files.
Marking required fields as optional is not the only difference (and, in
proto2, that is not a particularly safe operation -- you must be certain
you've updated *all* readers of those messages with the new
Hi,
I had a debate with my colleagues regarding to upgrade protobuf v3 because
I'd like to use MessageToJsonString and JsonStringToMessage for GUI
development of web application and mobile app, but my colleagues are not
convinced, they argued GO can do it very easily and they are worrying
