Message fields can never have implicit presence, but we have logic in ClearField that deallocates the message field and reassigns nullptr if the field is a "proto3" field. This snippet is the remnants of an old implementation of message field reflection when proto3 was first introduced (when the initial idea is to use open structs for everything). During implementation however, we ended up preserving explicit presence behavior for message fields. PiperOrigin-RevId: 691199008pull/19037/head
parent
25f6eabb76
commit
774a10798c
1 changed files with 1 additions and 10 deletions
Loading…
Reference in new issue