Skip to content
This repository has been archived by the owner on Jul 7, 2020. It is now read-only.

Use keyed fields in struct literals to appease go vet on Google AppEngine #20

Closed
wants to merge 1 commit into from
Closed

Use keyed fields in struct literals to appease go vet on Google AppEngine #20

wants to merge 1 commit into from

Conversation

leighmcculloch
Copy link
Contributor

What

Use keyed fields in struct literals.

Why

When pushing code to Google AppEngine that uses rsc.io/pdf, the code is
rejected with the error:

rsc.io/pdf/read.go:1055:9: composite struct literal crypto/cipher.StreamReader with unkeyed fields

I don't see this error locally with go1.9, and assume this is a feature
of go vet that has improved since go1.8.

…gine

What
===
Use keyed fields in struct literals.

Why
===
When pushing code to Google AppEngine that uses rsc.io/pdf, the code is
rejected with the error:

rsc.io/pdf/read.go:1055:9: composite struct literal crypto/cipher.StreamReader with unkeyed fields

I don't see this error locally with go1.9, and assume this is a feature
of go vet that has improved since go1.8.
leighmcculloch added a commit to leighmcculloch/clippercard that referenced this pull request Dec 31, 2017
leighmcculloch added a commit to leighmcculloch/clippercard that referenced this pull request Jan 1, 2018
leighmcculloch added a commit to leighmcculloch/clippercard that referenced this pull request Jan 1, 2018
Repository owner deleted a comment from leighmcculloch Jan 12, 2018
@rsc rsc closed this in 34a1e87 Jan 12, 2018
@leighmcculloch
Copy link
Contributor Author

Thanks for accepting the fix! ❤️

@leighmcculloch leighmcculloch deleted the fix-unkeyed-fields-go-vet-error branch January 19, 2018 08:04
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant