A pure Rust library to serialize/deserialize protobuf files.
This library intends to provide a simple yet fast (minimal allocations) protobuf parser implementation.
It provides both:
- pb-rs, a code generation tool:
- each .proto
file will generate a minimal rust module (one function to read, one to write, and one to compute the size of the messages)
- each message will generate a rust struct where:
- bytes
fields are converted to Cow::Borrowed([u8])
- string
fields are converted to Cow::Borrowed(str)
- repeated
fields are converted to Vec
- all other fields are converted into the matching rust primitive type
- no need to use google protoc
tool to generate the modules
- quick-protobuf, a protobuf file parser:
- this is the crate that you will typically refer to in your library. The generated modules will assume it has been imported.
- it acts like an event parser, the logic to convert it into struct is handle by pb-rs
pb-rs
binary, located into codegen
directory to automatically generate a foobar.rs module from a foobar.proto proto filesh
git clone https://github.com/tafia/quick-protobuf
cd quick-protobuf/codegen
cargo run ../../protobuf_example/foo_bar.proto
cd ../../protobuf_example
```toml
[dependencies] quick-protobuf = "0.2.0" ```
```rust // main.rs or lib.rs extern crate quick_protobuf;
mod foo_bar; // (see 1.)
use quick_protobuf::Reader;
// We will suppose here that Foo and Bar are two messages defined in the .proto file // and converted into rust structs // // FooBar is the root message defined like this: // message FooBar { // repeated Foo foos = 1; // repeated Bar bars = 2; // } use foo_bar::{FooBar};
fn main() { // create a reader, which will parse the protobuf binary file and pop events // this reader will read the entire file into an internal buffer let mut reader = Reader::from_file("/path/to/binary/protobuf.bin") .expect("Cannot read input file");
// use the generated module fns with the reader to convert your data into rust structs
let foobar = reader.read(FooBar::from_reader).expect("Cannot read FooBar message");
println!("Found {} foos and {} bars!", foobar.foos.len(), foobar.bars.len());
} ```
You can find basic examples in the examples directory. - codegen_example: A basic write/read loop on all datatypes
``` enum FooEnum { FIRSTVALUE = 1; SECONDVALUE = 2; }
message BarMessage { required int32 brequiredint32 = 1; }
message FooMessage { optional int32 fint32 = 1; optional int64 fint64 = 2; optional uint32 fuint32 = 3; optional uint64 fuint64 = 4; optional sint32 fsint32 = 5; optional sint64 fsint64 = 6; optional bool fbool = 7; optional FooEnum fFooEnum = 8; optional fixed64 ffixed64 = 9; optional sfixed64 fsfixed64 = 10; optional fixed32 ffixed32 = 11; optional sfixed32 fsfixed32 = 12; optional double fdouble = 13; optional float ffloat = 14; optional bytes fbytes = 15; optional string fstring = 16; optional FooMessage fselfmessage = 17; optional BarMessage fbarmessage = 18; repeated int32 frepeatedint32 = 19; repeated int32 frepeatedpacked_int32 = 20 [ packed = true ]; } ```
```rust
pub enum FooEnum { FIRSTVALUE = 1, SECONDVALUE = 2, }
pub struct BarMessage { // all fields are owned: no lifetime parameter pub brequiredint32: i32, }
pub struct FooMessage<'a> { // has borrowed fields: lifetime parameter
pub fint32: Option
message A {
message B {
// ...
}
}
As rust does not allow a struct and a module to share the same name, we use mod_Name
for the nested messages.
```rust
pub struct A {
//...
}
pub mod mod_A { pub struct B { // ... } } ```
package a.b;
Here we could have used the same name, but for consistency with nested messages, modules are prefixed with mod_
as well.
rust
pub mod mod_a {
pub mod mod_b {
// ...
}
}
This library is an alternative to the widely used rust-protobuf.
Pros
Cow<[u8]>
and Cow<str>
)Cons
Option
s unwrapping yourselfCow
as well if you want to modify itHave a look at the different generated modules for the same .proto file: - rust-protobuf: 2322 loc - quick-protobuf: 300 loc
The only implemented benchmarks are the adaptation from rust-protobuf perftest.
They show that quick-protobuf is, at the time of writing and on these specific benches much faster.
Any help is welcomed! (Pull requests of course, bug report, missing functionality etc...)
MIT