Joe Tsai 559d47f1da cmd/protoc-gen-go: fix init order for v1 registration ... The v1 registration leaks the message types out to the proto package. When doing that, it must ensure that the reflection data structures for those types are properly initialized first. We achieve that by doing v1 registration at the end of the reflection init function. Change-Id: If6df18df59d05bad50ff39c2eff6beb19e7466cc Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/168348 Reviewed-by: Damien Neil <dneil@google.com>		2019-03-20 04:16:33 +00:00
..
annotations	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
comments	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
extensions	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
fieldnames	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
import_public	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
imports	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
issue780_oneof_conflict	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
nopackage	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
proto2	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
proto3	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
gen_test.go
go.mod	all: fix travis after v1 update	2019-03-12 00:05:04 +00:00