tree d2b15bebb72dd7a2a2e37d09a360cf3de653ea90
parent e0790a756e9ba77e2d3d6ef5d0abbb11dd71211b
author Ian Lance Taylor <iant@golang.org> 1578552511 -0800
committer Ian Lance Taylor <iant@golang.org> 1578585487 +0000

compiler: don't add composite literal keys to package bindings

Adding composite literal keys to package bindings gets confusing when
it is combined with dot imports.  The test case showing the resulting
compilation failure is https://golang.org/cl/213899.

Fix this by adding a new expression type to hold composite literal keys.
We shouldn't see it during lowering if it is a struct field name,
because Composite_literal_expression::do_traverse skips struct field names.
Or, it should, but that didn't quite work with pointer types so it had to
be tweaked.

This lets us remove the code that recorded whether an Unknown_expression
is a composite literal key.

Change-Id: Ida38800a17dcd0bc0e47f636e021d5f2d4fc191d
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/214017
Reviewed-by: Than McIntosh <thanm@google.com>