protobuf-go/cmd/protoc-gen-go/testdata/extensions
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
..
base cmd/protoc-gen-go: enforce init order within packages 2019-03-10 22:19:14 +00:00
ext cmd/protoc-gen-go: correlate v1 ExtensionDesc with v2 ExtensionType 2019-03-15 01:24:42 +00:00
extra cmd/protoc-gen-go: enforce init order within packages 2019-03-10 22:19:14 +00:00
proto3 cmd/protoc-gen-go: correlate v1 ExtensionDesc with v2 ExtensionType 2019-03-15 01:24:42 +00:00