tree 84a375a467e21596198da17963731c373c0bd841
parent 32c79afd486f36024c9b989bd3445a7c83fc2ce0
author Damien Neil <neild@users.noreply.github.com> 1537397219 -0700
committer GitHub <noreply@github.com> 1537397219 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJbotHjCRBK7hj4Ov3rIwAAdHIIAH0yUUQtbSy+Hob9Q4cmp2s+
 uAzrxaxeZNN69S+9hk6OwMbuK2xdBjaRCHvmJReBECISo6NqgxTRqTDMWqH2Eaij
 DwxCxXvFoH8Fh3q9l6LpBw/686doyBtxDZsHNnZ/Z/jR032CNLvupHzZ+wNoRaqT
 sAGwzZhvchD6fFf6gKWwoLSjxwP8d/EZCAqb5M/uO5uAMGdq5AkALqSO9PnGPoAT
 a+nM11xLYRWHkbQpaO36NG3NwdMqtIBU5tJUYeNxcMkLQV6YGX7rFKcsFpv8fhcA
 TUm4+S9lSyQ5JFB/PCUqhE98JP2TQWUZN3ExMzWVfxIPsdHKRQf6yqhHAIkB+4o=
 =uaim
 -----END PGP SIGNATURE-----
 

protoc-gen-go: simplify init function generation (#716)

We generate a single init function containing registration calls for
all the things in a .pb.go that need one (messages, extensions, etc.)

Some of these registrations are added to a list as the generator processes
the type that needs to be registered (e.g., messages.) Some are added at
the end while generating the init function (e.g., enums). Extensions
are done in both places.

Make this consistent and always generate the registration functions
during processing. This simplifies the code a bit, and makes it easier
for a new generator to be consistent with its output.

No changes to the number of init functions, just the order of
registration calls in the existing one.