Joe Tsai afb455eaf8 cmd/protoc-gen-go: correlate v1 ExtensionDesc with v2 ExtensionType ... Unfortunately a good amount of code uses pointer comparisons on the v1 ExtensionDesc to determine exactly which extension field is set, rather than checking whether the extension descriptor semantically describes the field that they are interested in. To preserve this behavior in v1, we need a 1:1 mapping between a v2 ExtensionType and a specific v1 ExtensionDesc. Change-Id: I852b3cefb4585bd656e48e5adad6cc28795d02df Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/167759 Reviewed-by: Damien Neil <dneil@google.com>		2019-03-15 01:24:42 +00:00
..
enum.go	internal/prototype: move from reflect/prototype	2019-03-13 20:17:00 +00:00
export.go	internal/fileinit: generate reflect data structures from raw descriptors	2019-01-30 01:33:46 +00:00
extension_test.go	internal/prototype: move from reflect/prototype	2019-03-13 20:17:00 +00:00
extension.go	cmd/protoc-gen-go: correlate v1 ExtensionDesc with v2 ExtensionType	2019-03-15 01:24:42 +00:00
file_test.go	reflect/protoreflect: add HasJSONName, ReservedRanges, and ReservedNames	2018-12-07 20:10:15 +00:00
file.go	internal/legacy: use proto.Unmarshal from v2	2019-03-14 21:46:02 +00:00
message.go	internal/prototype: move from reflect/prototype	2019-03-13 20:17:00 +00:00