707894e869
This CL switches the integration test to be written in Go instead of bash. The benefits are: * The logic for setting up the dependencies is more robust and handles better a situation where the dependency failed to initialize (due to network trouble, FS permission problems, etc). * The logic does a better job at cleaning up stale dependencies. For example, my .cache folder has go1.9.4, go1.9.5, go1.10.5, and go1.10.6 folders even though we don't use them anymore. * Being able to run only a subset of the integration test since you can pass "-run" to the script. * A signifcant amount of complexity in the test.bash script was running the tests in parallel. This is trivial to do in Go. The major detriment is that Go is more verbose as a "scripting" language. Change-Id: Id7e5b303fb305fdbc0368bdf809dbf29fca1d983 Reviewed-on: https://go-review.googlesource.com/c/164861 Reviewed-by: Herbie Ong <herbie@google.com>
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.