Skip to content

Avoid go vet errors of "composite literal uses unkeyed fields" in tutorial #12

Description

@danackerson

by including X & Y field names in engo.Point declarations (e.g. in traffic.go demo).

Position: engo.Point{X: 10, Y: 10},

Definitely a very minor issue, but it cost me a few minutes trying to find out what the error meant and how to fix it.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions