8cb9190264
According to linguistics, this is actually a concrete syntax tree, rather than an abstract syntax tree since it perfectly represents the grammatical structure of the original raw input. On the other hand, an abstract syntax tree (AST) loses some grammatical structure and is only concerned with preserving syntax. See https://eli.thegreenplace.net/2009/02/16/abstract-vs-concrete-syntax-trees/ Change-Id: Ia3fdb407d2b15c5431984956b7d74921891c2ad9 Reviewed-on: https://go-review.googlesource.com/133995 Reviewed-by: Herbie Ong <herbie@google.com> |
||
---|---|---|
cmd/protoc-gen-go | ||
internal | ||
protogen | ||
reflect | ||
.gitignore | ||
.travis.yml | ||
AUTHORS | ||
CONTRIBUTING.md | ||
CONTRIBUTORS | ||
go.mod | ||
go.sum | ||
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.