code review 5534077: gc: don't print implicit type on struct literal in export

gc: don't print implicit type on struct literal in export

As pointed out in the discussion around 2678.

[lvd, 2012-02-01 13:17:37]

Hello rsc@golang.org (cc: golang-dev@googlegroups.com),

I'd like you to review this change to
https://go.googlecode.com/hg/

[rsc, 2012-02-03 17:40:24]

It looks like you started making implicit a 3-valued field
but didn't actually end up needing all 3 values.
Revert to the old true/false, drop the enum?

[lvd, 2012-02-03 17:43:57]

forgot to edit go.y, it uses the 3rd one

On Fri, Feb 3, 2012 at 18:40, Russ Cox <rsc@golang.org> wrote:
> It looks like you started making implicit a 3-valued field
> but didn't actually end up needing all 3 values.
> Revert to the old true/false, drop the enum?

[lvd, 2012-02-03 17:46:24]

On Fri, Feb 3, 2012 at 18:43, Luuk van Dijk <lvd@google.com> wrote:
> forgot to edit go.y, it uses the 3rd one

and that was really the whole crux: the ->implicit set in go.y on OIND
means something different than all the other ones.   this was really
the simplest fix, i tried reorganizing the representation of
OPTRLIT/OSTRUCTLIT but that just becomes way messier.

>
> On Fri, Feb 3, 2012 at 18:40, Russ Cox <rsc@golang.org> wrote:
>> It looks like you started making implicit a 3-valued field
>> but didn't actually end up needing all 3 values.
>> Revert to the old true/false, drop the enum?

[rsc, 2012-02-03 17:55:48]

LGTM

there is an = 2 in go.y 
that should be = ImplPtr

[lvd, 2012-02-06 11:20:03]

*** Submitted as http://code.google.com/p/go/source/detail?r=886ac920d2b9 ***

gc: don't print implicit type on struct literal in export

As pointed out in the discussion around 2678.

R=rsc
CC=golang-dev
http://codereview.appspot.com/5534077