Google Git
Sign in
go / protobuf / b9365044835d44830d1fc7fffd96e438761a98dc
commitb9365044835d44830d1fc7fffd96e438761a98dc[log] [tgz]
authorJoe Tsai <joetsai@digital-static.net>Tue Mar 19 14:14:29 2019 -0700
committerJoe Tsai <thebrokentoaster@gmail.com>Tue Mar 19 23:48:09 2019 +0000
treebed004a1cdfce7afafb256cbd44bb621ba9b350e
parent08cd8842f1937d1f81f7c558bfbabb0e58836513 [diff]
internal/legacy: guarantee one-to-one generation of wrapper types

When concurrent requests to wrap a type occurs, it is possible that
two different descriptors are created for the same Go type.
Add sufficient synchronization to ensure that one descriptor is ever
returned for one Go type.

Change-Id: Idbbca4c1877a70317b39900ae83bfc3085d4a9c5
Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/168398
Reviewed-by: Herbie Ong <herbie@google.com>
5 files changed
tree: bed004a1cdfce7afafb256cbd44bb621ba9b350e
  1. cmd/
  2. encoding/
  3. internal/
  4. proto/
  5. protogen/
  6. reflect/
  7. runtime/
  8. types/
  9. .gitignore
  10. .travis.yml
  11. AUTHORS
  12. CONTRIBUTING.md
  13. CONTRIBUTORS
  14. go.mod
  15. go.sum
  16. integration_test.go
  17. LICENSE
  18. PATENTS
  19. README.md
  20. regenerate.bash
  21. test.bash
README.md

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.