d24bc72368
The protobuf type system uses the word "descriptor" instead of "type". We should avoid the "type" verbage when we aren't talking about Go types. The old names are temporarily kept around for compatibility reasons. Change-Id: Icc99c913528ead011f7a74aa8399d9c5ec6dc56e Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/172238 Reviewed-by: Herbie Ong <herbie@google.com> 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.