vtprotobuf

vtprotobuf copied to clipboard

The current `equal` implementation generates code that recognizes a `nil` message as being equal to an empty message of the same type. However, [this is not how `proto.Equal` works](https://github.com/protocolbuffers/protobuf-go/blob/v1.28.1/proto/equal.go#L42), where...

misberner

The existing implementation of `CloneVT` was silently discarding unknown fields, breaking some basic assumptions (such that a clone should always be equal to the original). Thus, extend the test generation...

misberner

Avoid proto reflection for builtin types

6

The optimized generated code for marshal, unmarshal, clone etc. still resorts to generic, `protoreflect`-based logic for builtin/well-known types such as `google.protobuf.Timestamp`, `google.protobuf.Duration` etc. Since these types are well known, it...

misberner

Hello! We in [gowaves](https://github.com/wavesplatform/gowaves) use this plug-in to marshal messages for producing signatures futher and compare them to signed messages which would be marshalled by other languages implementations. The problem...

artemreyt

Fix bugs where pooling slices are not reused

1

hueypark

Unable to get pooling methods to gen

8

I am currently attempting to put together a POC for using vtprotobuf in an application I work on. However the most promising feature (pooling) does not seem to exist in...

joe-elliott

Add support for pools for oneof fields

5

I have implemented the minimal changes necessary for pools to work with oneof fields because the generated code currently does not compile. If needed, I can work on improving the...

maticz

TinyGo support

1

First off, wanted to say thanks for such a great project. While the issue title may sound like a feature request, the code generated by vtprotobuf already works with TinyGo....

kyleconroy

gRPC and pooling

1

I have a couple of questions regarding pooling and gRPC that I could not fully understand from existing issues or the readme. (happy to do a PR to clarify in...

brancz

Incorrect generation of "optional" parameters in the "response" message

1

Hi I tried to return the optional field in the rpc response message and got the wrong generation

flymedllva