The intent is to avoid codegen issues for simple cases where a message of the shape: message M { int32 x = 3 string set_x = 8; } Which would otherwise break due to the first field having a setter whose name collides with the second field's getter. By seeing that 'set_x' matches another field with a common accessor prefixed, it will generate all accessors for that field as though it was named `set_x_8`. This does not avoid all possible collisions, but should mitigate the vast majority of situations of an accidental collision. PiperOrigin-RevId: 627776907pull/16591/head
parent
849b975e5f
commit
55875598f7
12 changed files with 119 additions and 32 deletions
Loading…
Reference in new issue