Google Git
Sign in
go / protobuf / 124c8121e1e9410c0d292882ea215c0cb09ec456
commit124c8121e1e9410c0d292882ea215c0cb09ec456[log] [tgz]
authorJoe Tsai <joetsai@digital-static.net>Mon Jan 14 11:48:43 2019 -0800
committerJoe Tsai <thebrokentoaster@gmail.com>Mon Jan 14 20:10:11 2019 +0000
treeb8d3e672bb574549c9b147c75f7b1522e60364cf
parentd18bd3183863308a7234f80cd501e519ac8c7def [diff]
protogen: use types.Universe.Names for list of builtin identifiers

Rather than maintaining our own list of builtin Go identifiers, use the
types.Universe API in the standard library instead.

It is okay if this list of names changes over time since we use this only
to derive a locally-used package name in the generated file.

Change-Id: Ib1688abc47d5c97b557f6e1f4d60c78e0951e65b
Reviewed-on: https://go-review.googlesource.com/c/157818
Reviewed-by: Damien Neil <dneil@google.com>
2 files changed
tree: b8d3e672bb574549c9b147c75f7b1522e60364cf
  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. LICENSE
  17. PATENTS
  18. README.md
  19. regenerate.bash
  20. 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.