protobuf

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

Adam Cozzette 6ab302d3a3 Rust: cut down on the amount of generated C++ code needed for maps With the C++ kernel for Rust, we currently need to generate quite a few C++ thunks for operations on map fields. For each message we generate, we generate these thunks for all possible map types that could have that message as a value. These operations are for things such as insertion, removal, clearing, iterating, etc. The reason we do this is that templated types don't play well with FFI, so we effectively need separate FFI endpoints for every possible combination of key and value types used (or even potentially used) as a map field. This CL fixes the problem by replacing the generated thunks with functions in the runtime that can operate on `proto2::MessageLite*` without needing to care about the specific message type. The way it works is that we implement the operations using either `UntypedMapBase` (the base class of all map types, which knows nothing about the key and value types) or `KeyMapBase`, which knows the key type but not the value type. I roughly followed the example of the table-driven parser, which has a similar problem of needing to operate generically on maps without having access to the concrete types. I removed 54 thunks per message (that's 6 key types times 9 operations per key), but had to add two new thunks per message: - The `size_info` thunk looks up the `MapNodeSizeInfoT`, which is stored in a small constant table. The important thing here is an offset indicating where to look for the value in each map entry. This offset can be different for every pair of key and value types, but we can safely assume that the result does not depend on the signedness of the key. As a result we only need to store four entries per message: one each for i32, i64, bool, and string. - The `placement_new` thunk move-constructs a message in place. We need this to be able to efficiently implement map insertion. There are two big things that this CL does not address yet but which I plan to follow up on: - Enums still generate many map-related C++ thunks that could be replaced with a common implementation. This should actually be much easier to handle than messages, because every enum has the same representation as an i32. - We still generate six `ProxiedInMapValue` implementations for every message, but it should be possible to replace these with a blanket implementation that works for all message types. PiperOrigin-RevId: 657681421		6 months ago
..
utf8	Introduce a prelude and remove the inherent impls for serialize()	6 months ago
BUILD	Rust: update map setters to take `IntoProxied`	6 months ago
accessors_map_test.rs	Rust: cut down on the amount of generated C++ code needed for maps	6 months ago
accessors_proto3_test.rs	Add Message::Clear() and MessageMut::Clear() (behind the Clear trait)	6 months ago
accessors_repeated_test.rs	…
accessors_test.rs	Add Message::Clear() and MessageMut::Clear() (behind the Clear trait)	6 months ago
bad_names_test.rs	…
child_parent_test.rs	Introduce a prelude and remove the inherent impls for serialize()	6 months ago
ctype_cord_test.rs	…
edition2023_test.rs	…
enum_test.rs	…
fields_with_imported_types_test.rs	…
import_public_test.rs	…
merge_from_test.rs	…
nested_types_test.rs	…
package_disambiguation_test.rs	…
package_test.rs	…
proto_macro_test.rs	…
serialization_test.rs	Introduce a prelude and remove the inherent impls for serialize()	6 months ago
simple_nested_test.rs	…