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

Tag: Branch: Tree: d692223887

Author	SHA1	Message	Date
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