Google Git
Sign in
go / protobuf / 095e23da3166239d8d4fd5a9832e413b25d65fb6
commit095e23da3166239d8d4fd5a9832e413b25d65fb6[log] [tgz]
authorJoe Tsai <joetsai@digital-static.net>Wed May 22 04:55:11 2019 -0400
committerJoe Tsai <joetsai@digital-static.net>Wed May 22 14:35:38 2019 +0000
tree2b7c193a99359b1fbe56c05ebdb98398be612f84
parentfb30a40376ac80737bcdadf6ff08a2caab24a761 [diff]
internal/impl: drop legacy prefix for some files

Both legacy_unknown.go and legacy_extension.go deal with the
current data structure for unknown fields and extensions.
While the current data structure is sub-optimial,
strictly speaking, they are not "legacy" since they are very much
used by the v2 API as well.

Change-Id: I3852dba0dcebaee00bbeb94d9936cd759f774f0a
Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/178477
Reviewed-by: Damien Neil <dneil@google.com>
2 files changed
tree: 2b7c193a99359b1fbe56c05ebdb98398be612f84
  1. cmd/
  2. compiler/
  3. encoding/
  4. internal/
  5. proto/
  6. reflect/
  7. runtime/
  8. testing/
  9. types/
  10. .gitignore
  11. .travis.yml
  12. AUTHORS
  13. CONTRIBUTING.md
  14. CONTRIBUTORS
  15. go.mod
  16. go.sum
  17. integration_test.go
  18. LICENSE
  19. PATENTS
  20. README.md
  21. regenerate.bash
  22. 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.