quick-protobuf icon indicating copy to clipboard operation
quick-protobuf copied to clipboard

A rust implementation of protobuf parser

Results 72 quick-protobuf issues
Sort by recently updated
recently updated
newest added

Hi I was looking at https://crates.io/crates/quick-protobuf and saw a new release came out, 0.7.0. There doesn't seem to be a tag in this repo for that release, and also the...

hi, trying to generate a simple message with 2 strings i.e. ```protobuf syntax = "proto2"; message HelloRequest { required string one = 1; required string two = 2; } ```...

I made a repo to reproduce the issue here: https://github.com/benma/quick-protobuf-issue pb-rs seems to have trouble with imports in this scenario: common.proto: ```protobuf syntax = "proto3"; message Common { } ```...

In this combination, those imports are missing: ``` use alloc::borrow::ToOwned; use alloc::string::String; ``` Those are not imported by default in no_std.

Hi, I've found that .proto cannot be parsed by `pb-rs`, but work fine in `protoc-rust`. Here's archive with working example crate: [bug.zip](https://github.com/tafia/quick-protobuf/files/4233815/bug.zip) Basically, there's two proto files in the same...

All examples and code I see assume there's only one .proto file. What is recommended way to compile .proto to .rs files, if we have thousands of input .proto files?

- Path::new needs to take a reference - RpcGeneratorFunction is not pulled in from pb_rs::types - custom_includes is not specified - owned is not specified

I'm curious whether you've considered using the [bytes crate](https://crates.io/crates/bytes) for handling of `&[u8]` buffers should also allow to get rid of `std::cow` for strings. This might provide for a nicer...

Simpler reading of emitted source for values under 8 (and simpler reading of emitted type values regardless). Mostly a readability thing for outputted code.