protobuf

Commit Graph

Author	SHA1	Message	Date
Protobuf Team Bot	dd4ffc65cc	Internal Code Change PiperOrigin-RevId: 550163810	1 year ago
Marcel Hlopko	3ced818640	Add support for proto_library with more than one srcs If a proto_library has more than one srcs, we designate the first one as the primary (that file will be passed to rustc as the crate root). All other files will represent (internal) submodules of the crate. In general, Rust users won't see which .proto file a message came from, they will only see a crate corresponding to the entire proto_library, and in it public submodules for all `package` statements in all .proto files in the proto_library sources. Therefore in this CL we reexport all messages from non primary sources into their corresponding public modules (= packages declared in their owning .proto files). Besides the common case this CL also handles .proto files without package statement, and a subset of behaviors needed for public import functionality. PiperOrigin-RevId: 549543321	1 year ago
Hong Shin	b01794cb3b	Add test that ensures rust protos build with reserved keywords Also confirmed that this fails to build without the `r#` inside singular_scalar.cc PiperOrigin-RevId: 546906226	1 year 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	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
Marcel Hlopko	f7a2f4acea	Add initial end-to-end test directory structure. This turns out to be quite of a yak shave to be able to perfectly test both kernels without having to pass extra Blaze flags. PiperOrigin-RevId: 521850709	2 years ago
Jakob Buchgraber	7802b93442	Fix build errors in Protobuf Rust PiperOrigin-RevId: 518619271	2 years ago
Protobuf Team Bot	f73c7cb74a	Add license rules PiperOrigin-RevId: 518370510	2 years ago
Marcel Hlopko	aaa338b285	Configure build for the C++ backend PiperOrigin-RevId: 517429571	2 years ago
Marcel Hlopko	ab9f1ab58a	Configure the build for the Rust UPB backend In this CL we're adding the barebones infrastructure to generate Rust proto messages using UPB as a backend. The API is what we call a V0, not yet production-quality, not yet rigorously designed, just something to enable parallel work. The interesting part of switching backend between UPB and C++ will come in a followup. PiperOrigin-RevId: 517089760	2 years ago
Marcel Hlopko	5252bc8ec8	Rename a test PiperOrigin-RevId: 515628124	2 years ago
Marcel Hlopko	26af540a7a	Add support for proto dependencies to rust_proto_library PiperOrigin-RevId: 514719215	2 years ago
Marcel Hlopko	3dc546daff	Implement a minimal, internal, experimental rust_proto_library rule. The internal design is consistent with other <lang>_proto_library rules. rust_proto_library attaches rust_proto_library_aspect on its `deps` attribute. The aspect traverses the dependency, and when it visits proto_library (detected by ProtoInfo provider) it registers 2 actions: 1) to run protoc with Rust backend to emit gencode 2) to compile the gencode using Rustc Action (2) gets the Rust proto runtime as an input as well. Coming in a followup is support and test coverage for proto_library.deps. PiperOrigin-RevId: 514521285	2 years ago

13 Commits (881f56a8760b44cbc3e14479ef6372f4d7173678)