protobuf

Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/

Jakob Buchgraber 68da9337b4 Remove 'assert_c_type_sizes' test The test I am removing fails on 32-bit ARM, as pointers are 4-byte aligned. `upb_MessageValue` is a union. The alignment of a union is the max. alignment of any of its fields. Among the fields are 8-byte types like u64 and thus `upb_MessageValue` is 8-byte aligned even on 32-bit ARM. 4 != 8 and it fails. I am split on the usefulness of the test, as I find it somewhat unlikely to catch any divergence between the FFI and C types in the future. I can't imagine a practical scenario where upb_MessageValue would change in C code and this test would fail. IMO our actual unit & integration tests plus the IFTT lints are much better guards. We could fix the test by testing the alignment of u64 instead of *const c_void, which is always 8 bytes on the hw platforms we care about. PiperOrigin-RevId: 638976482		8 months ago
..
cpp_kernel	Accept MessageLite type instead of the Message type in SerializeMsg	8 months ago
test	Make serialization correctly be fallible in the Rust Protobuf API.	8 months ago
upb	…
BUILD	…
aspects.bzl	Internal change.	8 months ago
cpp.rs	…
defs.bzl	Internal change.	8 months ago
enum.rs	…
internal.rs	…
map.rs	…
optional.rs	…
primitive.rs	…
proto_macro.rs	…
protobuf.rs	…
proxied.rs	…
repeated.rs	…
shared.rs	Make serialization correctly be fallible in the Rust Protobuf API.	8 months ago
string.rs	…
upb.rs	Remove 'assert_c_type_sizes' test	8 months ago
utf8.rs	…