50c16719d7
The v2 implementation will eagerly unmarshal extension fields, which means that the logic to synchronize the extensions fields is no longer necessary. Using type aliases, we can ensure impl.ExtensionsV1 is identical to the extensions map prior to a4ab9ec5 from May 2016. This makes it such that we only have one legacy implementation that we have to deal with. Change-Id: I41b977e912fbb899c5bc4f055890d474b419429c Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/172240 Reviewed-by: Damien Neil <dneil@google.com> |
||
---|---|---|
cmd | ||
encoding | ||
internal | ||
proto | ||
protogen | ||
reflect | ||
runtime | ||
types | ||
.gitignore | ||
.travis.yml | ||
AUTHORS | ||
CONTRIBUTING.md | ||
CONTRIBUTORS | ||
go.mod | ||
go.sum | ||
integration_test.go | ||
LICENSE | ||
PATENTS | ||
README.md | ||
regenerate.bash | ||
test.bash |
Next Generation Go Protocol Buffers
WARNING: This repository is in active development. There are no guarantees about API stability. Breaking changes will occur until a stable release is made and announced.
This repository is for the development of the next major Go implementation of protocol buffers. This library makes breaking API changes relative to the existing Go protobuf library. Of particular note, this API aims to make protobuf reflection a first-class feature of the API and implements the protobuf ecosystem in terms of reflection.
Design Documents
List of relevant design documents:
Contributing
We appreciate community contributions. See CONTRIBUTING.md.
Reporting Issues
Issues regarding the new API can be filed at
github.com/golang/protobuf.
Please use a APIv2:
prefix in the title to make it clear that
the issue is regarding the new API work.