Matthew Dempsky f422bea498 cmd/compile: fix compile failure for lazily resolved shadowed types ... If expanding an inline function body required lazily expanding a package-scoped type whose identifier was shadowed within the function body, the lazy expansion would instead overwrite the local symbol definition instead of the package-scoped symbol. This was due to importsym using s.Def instead of s.PkgDef. Unfortunately, this is yet another consequence of the current awkward scope handling code. Passes toolstash-check. Fixes #25984. Change-Id: Ia7033e1749a883e6e979c854d4b12b0b28083dd8 Reviewed-on: https://go-review.googlesource.com/120456 Run-TryBot: Matthew Dempsky <mdempsky@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Reviewed-by: Robert Griesemer <gri@golang.org>		2018-06-22 17:57:09 +00:00
..
p.go	cmd/compile: fix compile failure for lazily resolved shadowed types	2018-06-22 17:57:09 +00:00
q.go	cmd/compile: fix compile failure for lazily resolved shadowed types	2018-06-22 17:57:09 +00:00