Damien Neil 44000a1bea cmd/protoc-gen-go: treat extensions fields as proto2 in some places ... The v1 generator doesn't include a "proto3" tag on extension fields, even when the field is defined in a proto3 file. Match that behavior for consistency. We can probably change this later if we want to; it's unlikely anyone is depending on this behavior. The v1 generator uses pointer types for extension fields, even when the field is defined in a proto3 file. (e.g., *FooEnum instead of FooEnum.) Match this behavior. We can't change this without breaking compatibility in the generated code. Change-Id: I4072f3dd1c915bf9ab89f1d5198e0144cb4de20f Reviewed-on: https://go-review.googlesource.com/c/144282 Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com>		2018-10-24 19:46:45 +00:00
..
internal_gengo	cmd/protoc-gen-go: treat extensions fields as proto2 in some places	2018-10-24 19:46:45 +00:00
testdata	cmd/protoc-gen-go: treat extensions fields as proto2 in some places	2018-10-24 19:46:45 +00:00
golden_test.go	protogen: generate .meta file with code annotations	2018-10-16 17:22:41 +00:00
main.go	protogen: add an option to rewrite import paths	2018-09-28 21:19:59 +00:00