tree d794a9bdc55de77d619f79ae5d610654ee34d4ed
parent 84395510fcbf63588d4fe6786d750dc874e37b18
author Damien Neil <dneil@google.com> 1546820954 -0800
committer Damien Neil <dneil@google.com> 1546903050 +0000

cmd/protoc-gen-go: don't chain public imports

Consider the case:

	a.proto publicly imports b.proto
	b.proto publicly imports c.proto

Should a.pb.go include symbols defined in c.pb.go?

Historically, it has not. As of #155677, it does. Regardless of which behavior
is preferable, #155677 produces broken code in some common situations: If
a.proto also publicly imports c.proto, we now generate two copies of the
forwarding decls for that file.

Restore the pre-#155677 behavior to avoid this breakage.

Change-Id: I283600b3be19eac2c3b3c14233bb69fa64661581
Reviewed-on: https://go-review.googlesource.com/c/156348
Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com>