68b81c3117
Change the storage type of ExtensionField from interface{} to protoreflect.Value. Replace the codec functions operating on interface{}s with ones operating on Values. Values are potentially more efficient, since they can represent non-pointer types without allocation. This also reduces the number of types used to represent field values. Additionally, this change lays groundwork for changing the user-visible representation of repeated extension fields from *[]T to []T. The storage type for extension fields must support mutation (thus *[]T currently); changing the storage type to a Value permits this without the need to introduce yet another view on field values. Change-Id: Ida336be14112bb940f655236eb58df21bf312525 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/192218 Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com> |
||
---|---|---|
benchmarks | ||
cmd | ||
compiler/protogen | ||
encoding | ||
internal | ||
proto | ||
reflect | ||
runtime | ||
testing/prototest | ||
types | ||
.gitignore | ||
.travis.yml | ||
AUTHORS | ||
CONTRIBUTING.md | ||
CONTRIBUTORS | ||
go.mod | ||
go.sum | ||
integration_test.go | ||
LICENSE | ||
PATENTS | ||
README.md | ||
regenerate.bash | ||
release.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.