What operating system and processor architecture are you using (go env)?
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
What did you do?
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered:
I'm going to re-open this. I think the suggestion is quite reasonable and syntactically it makes sense (but @quentinmit has a point, too). Not saying that I will do anything about it yet, but I want to think about this a bit.
Oh, cool. Thanks. There's a whole variety of ways to look at it, so I can understand opinion on where such a thing should go is going to differ for each person. I see the columns as 'name' and 'type', and so it makes logical sense to me that a name-less field should be lined up that way. The other side of the coin is that a nameless type uses the type as the name; ergo -- it's a name and belongs in the first column.
Last but not least, you can write the type twice as a workaround:
@Kroc This is not field with a nameless type, it's a field w/o an explicit field name. That is, rune in this case is the type. The work-around that you describe may work here (embedding of a predefined type w/o methods), but generally this is not correct for any type as the semantics of the struct change.