Comment #8 on issue 515 by wonhee.jung: More intelligent enums

Isn't it common practice to add UNKNOWN to be enum's 0th field to allow other side to pick it up as default value when there is a enum value that isn't their side but added in serialized message? This will instantly become issue when you add more than one UNKNOWN field in the enum that sibling each other.

Wrapping enum with another message looks ugly to me, and only simple way for this so far would be adding prefix for it, like

  UNKNOWN = 0;
  NONE = 1;
  USD = 2;
  // etc...

. Is there any other simple way that recently introduced in Protobuf?

You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:

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 post to this group, send email to
Visit this group at
For more options, visit

Reply via email to