unkeyed fields ?

[bsr]

What does this error indicates?

mail.go:79:11: composite struct literal net/mail.Address with unkeyed fields

and the line is 

net_mail.Address{"Support", "a...@b.com"},

net_mail is imported as 

net_mail "net/mail"

I searched for "unkeyed" in spec and couldn't find any result.

Thanks.

[uveli...@gmail.com]

net_mail.Address{Name: "Support",Address: "a...@b.com"}, maybe

> --
> You received this message because you are subscribed to the Google Groups "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
> For more options, visit http://mandrillapp.com/track/click.php?u=30146375&id=2e2b85d10e444b0591614e8f4561fc68&url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&url_id=0eff33bcce254e5290251b570e09b3a407331786.

[Dan Kortschak]

Can you post a minimal reproducer to the playground?:

--

You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[bsr]

thanks for the help. I am getting this error in app engine app. @Uvelichitel is right, the error went away by specifying the key. I  think the error is coming from go vet, and GAE made some stuff stricter in latest release (1.9.1).

[David Symonds]

It's not new. App Engine has been rejecting app code using unkeyed
composite struct literals since early 2012. The issue is that App
Engine wants to accept correct Go code at time T, but then still be
able to recompile it at time T+n, even if the language or standard
libraries have evolved in a backward-compatible way between those two
points in time. For that reason, it is in general strongly recommended
to use keyed composite struct literals in Go code that references
types in other packages, and we enforce that recommendation on App
Engine.

[jaim...@gmail.com]

Hey David. Your explanation makes perfect sense. However the DevAppServer seems to happily accept code with unkeyed fields in its recompile. And this only breaks at push time when one attempts to deploy their application.

I think the two should at least be consistent.

-Jaime

[David Symonds]

On 6 June 2014 02:36, <jaim...@gmail.com> wrote:

> Hey David. Your explanation makes perfect sense. However the DevAppServer
> seems to happily accept code with unkeyed fields in its recompile. And this
> only breaks at push time when one attempts to deploy their application.
>
> I think the two should at least be consistent.

You're right they should be consistent. I think I know why they aren't
(is the code using an unkeyed struct literal in your GOPATH?). Can you
file a bug on the issue track for this?