Avoid go vet
errors of "composite literal uses unkeyed fields" in tutorial
#12
Labels
go vet
errors of "composite literal uses unkeyed fields" in tutorial
#12
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.
The text was updated successfully, but these errors were encountered: