28e61ba70b
The aberrant support logic only has access to the Go type information, and not a concrete value. However, the XXX_MessageName method exists on some hacky dynamic proto implementations where it is only valid to call on a concrete value, not just newly created instance of the given type. However, from the perspective of the support logic, it is impossible to distinguish between dynamic messages and hand-crafted custom messages. Thus, just drop support for XXX_MessageName. We won't get the full name of the message right, but oh well, what can we do. Change-Id: Icc272861e11a355639fb82a991ca2854a9edc0c7 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/184557 Reviewed-by: Damien Neil <dneil@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.