protobuf

Commit Graph

Author	SHA1	Message	Date
Marcel Hlopko	836c5c3af5	Internal change PiperOrigin-RevId: 561268500	2 years ago
Alyssa Haroldsen	9a0bc392b3	Implement v0.6 Optional Bytes This makes a few changes: - It changes generated messages to reference message innards as a type in `__runtime` instead of branching on what fields should be there. That results in much less bifurcation in gencode and lets runtime-agnostic code reference raw message innards. - It adds a generic mechanism for creating vtable-based mutators. These vtables point to thunks generated for interacting with C++ or upb fields. Right now, the design results in 2-word (msg+vtable) mutators for C++ and 3-word mutators (msg+arena+vtable) for UPB. See upb.rs for an explanation of the design options. I chose the `RawMessage+&Arena` design for mutator data as opposed to a `&MessageInner` design because it did not result in extra-indirection layout changes for message mutators. We could revisit this in the future with performance data, since this results in all field mutators being 3 words large instead of the register-friendly 2 words. - And lastly, as a nearby change that touches on many of the same topics, it adds some extra SAFETY comments for Send/Sync in message gencode. PiperOrigin-RevId: 559483437	2 years ago
Protobuf Team Bot	1525300472	Replace `NonNull<u8>` for raw messages with a dedicated opaque pointer These are more type safe, and more clearly distinguish between a raw message and serialized data. This also defines a macro to create new opaque pointer types, and switches `RawArena` to using it. PiperOrigin-RevId: 552957136	2 years ago
Hong Shin	4f20efbb78	Internal Change PiperOrigin-RevId: 546867607	2 years ago
Protobuf Team Bot	5a48187464	Move internal-only but kernel-agnostic paths into an `__internal` module Add some documentation along the way. PiperOrigin-RevId: 540311409	2 years ago
Marcel Hlopko	c0c66ec1ea	Internal change PiperOrigin-RevId: 538294711	2 years ago
Marcel Hlopko	f92edc13c2	Automated rollback of commit `fe7c4f9422`. PiperOrigin-RevId: 538128679	2 years ago
Marcel Hlopko	fe7c4f9422	Simplify Protobuf Rust runtime build setup PiperOrigin-RevId: 537300231	2 years ago
Marcel Hlopko	701e056e2b	Zhuzh up the C++/Rust interop test to demonstrate more uses. Taking over the work done by mcyoung@ PiperOrigin-RevId: 529063108	2 years ago
Marcel Hlopko	5091c9fd10	Enable sanitized CI builds PiperOrigin-RevId: 524773049	2 years ago
Marcel Hlopko	a1ba8d238a	Generate bindings under the correct package. Before this CL all messages were generated in the top-level crate module. With this change we generate messages under the module specified by the package declaration in the .proto file. Dots are interpreted as submodule separator in consistency with how C++ namespaces are handled. Note that name of the proto_library target still remains to be used as the crate name. This CL only adds crate submodules dependeing on the specified package. PiperOrigin-RevId: 524235162	2 years ago
Marcel Hlopko	777f84f559	Implement bool and int64 field accessors for v0 Rust API PiperOrigin-RevId: 523671732	2 years ago
Marcel Hlopko	390b7f3e6f	Implement Msg::parse(&mut self) for V0 API. PiperOrigin-RevId: 523665442	2 years ago
Marcel Hlopko	5814f6c977	Generate C++ thunks for Rust protos In this CL I'd like to call existing C++ Protobuf API from the V0 Rust API. Since parts of the C++ API are defined inline and using (obviously) C++ name mangling, we need to create a "thunks.cc" file that: 1) Generates code for C++ API function we use from Rust 2) Exposes these functions without any name mangling (meaning using `extern "C"`) In this CL we add Bazel logic to generate "thunks" file, compile it, and propagate its object to linking. We also add logic to protoc to generate this "thunks" file. The protoc logic is rather rudimentary still. I hope to focus on protoc code quality in my followup work on V0 Rust API using C++ kernel. PiperOrigin-RevId: 523479839	2 years ago

14 Commits (3e3c83f0ca6c73cd6f2513640b7ed04d911fbb25)