Chiebot-Mirror/protobuf - protobuf - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Joshua Haberman	339fdb5e7b	Hide `upb_MiniTableField.descriptortype` with `UPB_PRIVATE()` macro PiperOrigin-RevId: 524371449	2 years ago
Protobuf Team Bot	e275be2830	Guard deep copy sub table check from other uses of submsg_index. When copying array items only access and pass sub table if field type is message. PiperOrigin-RevId: 523268010	2 years ago
Joshua Haberman	df93cf65a2	Hide upb_MiniTableField.submsg_index with new `UPB_PRIVATE()` macro The fields of upb_MiniTableField are intended to be internal-only, accessed only through public functions like `upb_MiniTable_GetSubMessageTable()`. But over time, clients have started accessing many of these fields directly. This is an easy mistake to make, as there is no clear signal that the fields should not be used in applications. This makes the implementation difficult to change without breaking users. The new `UPB_PRIVATE()` macro appends an unpredictable string to each private symbol. This makes it very difficult to accidentally use a private symbol, since users would need to write something like `field->submsg_index_dont_copy_me__upb_internal_use_only`. This is still possible to do, but it leaves a clear wart in the code showing that an an encapsulation break has occurred. The `UPB_PRIVATE()` macro itself is defined in `port/def.inc`, which users cannot include directly. Once we land this, more such CLs will follow for the other fields of `upb_MiniTable*`. We will add inline functions as needed to provide the semantic functionality needed by users. PiperOrigin-RevId: 523166901	2 years ago
Protobuf Team Bot	d5c22624fe	Fix cloning of repeated upb_Array. PiperOrigin-RevId: 517280344	2 years ago
Protobuf Team Bot	3286f948f8	Implements upb_Message_DeepClone. PiperOrigin-RevId: 514723111	2 years ago