Google Git
Sign in
go / protobuf / a691404b5d99458624629846e6258ca01165b6bc
commita691404b5d99458624629846e6258ca01165b6bc[log] [tgz]
authorJoe Tsai <joetsai@digital-static.net>Tue Jul 02 17:38:37 2019 -0700
committerJoe Tsai <joetsai@digital-static.net>Wed Jul 03 16:36:09 2019 +0000
treeaadc60170e9eb56dac19da01ae2745d74daa7455
parent28216c7cf27e9c6c836383b549546c5334241ba7 [diff]
reflect/protodesc: return deep copies of the input

There is little performance benefit to aliasing the input since we copy
every field except the options. Thus, just go all the way and copy the
options as well and document this as such.

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