Comment change: clarifies that the field/value order is based on textual order in the file, not the order of the enums.
Clarifies that reordering `enum` fields (even without changing their IDs) will change the order of the `value` indices. (This means that a seemingly "no-op" change to reorganize enums may affect code that (incorrectly) relied on the order of `value()`. PiperOrigin-RevId: 688297400pull/18929/head
parent
84a4472a0f
commit
f92335b36d
1 changed files with 5 additions and 2 deletions
Loading…
Reference in new issue