rust-protobuf

rust-protobuf copied to clipboard

perf: fix encode_varint{32,64}

2

The previous code was full of jumps that aren't easily predictable. This version is less code, generates less code, and should perform better (well, on x86_64 anyway, I am not...

morrisonlevi

Fixes #704. Fixes #706. I wasn't sure how to add tests for either. For #704, I didn't see a way to distinguish which syntax was being used in a test....

rcorre

Given ``` syntax = "proto3"; package api; message Example { repeated uint32 i = 1; repeated string s = 2 [packed=true]; } ``` The pure parser crashes with `internal error:...

rcorre

Is it possible to enable generating rustdoc comments from proto comments? (Using // in .proto files) I use protobuf codegen in this way: ```rust protobuf_codegen::Codegen::new() .protoc() .customize(Customize::default().gen_mod_rs(false)) .out_dir(outdir()) .include("src/proto") .inputs(&paths)...

antonio-dropulic

Given the following proto file: ```proto3 syntax = "proto3"; package api; message Example { repeated uint32 i = 1; } ``` And the following rust code: ```rust let mut example...

rcorre

Codegen: option to use BTreeMap as map representation

8

As of now, protobuf maps are represented with [std::collections::HashMap](https://doc.rust-lang.org/stable/std/collections/struct.HashMap.html), which serves as a robust default. In rarer instances, opting for a different implementation, such as BTreeMap, might be desirable, e.g....

akhramov

impl From for MessageField for convenience

1

I have found that constructing various messages often leads to creating `MessageField` types explicitly. For example, the following struct may be generated: ```rust struct MyStruct { pub some_field: MessageField, ......

jkalez

How to deserialize a message with full dynamic implementation

2

Hi, I'd like to do a deserialize using a messageDescriptor. I can't use protobuf-codegen because my code has to be totally dynamic. Is there a method for performing this type...

gabangotti

In commit eae7ac4, module `parse_and_typecheck` visibility is set to crate and exposes the function `parse_and_typecheck_custom`, but its argument required Trait `ProtoPathResolver` is not exposed

teble

Hi, I am building a dynamic message from a dynamic file descriptor, and I noticed that the dynamic fds seem to ignore proto3 optional settings Steps to reproduce: 1. Build...

ruiQQ