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
..
any.pb.go	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
api.pb.go	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
duration.pb.go	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
empty.pb.go	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
field_mask.pb.go	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
source_context.pb.go	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
struct.pb.go	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
timestamp.pb.go	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
type.pb.go	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00
wrappers.pb.go	cmd/protoc-gen-go: fix init order for v1 registration	2019-03-20 04:16:33 +00:00