Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

go vet issues #49

Closed
stanim opened this issue Jul 7, 2015 · 0 comments · Fixed by #57
Closed

go vet issues #49

stanim opened this issue Jul 7, 2015 · 0 comments · Fixed by #57
Assignees

Comments

@stanim
Copy link
Collaborator

stanim commented Jul 7, 2015

Draw2d contains some issues reported by go vet, which likely should be fixed:

arc.go:38: unreachable code
arc.go:67: unreachable code
arc.go:59: code.google.com/p/freetype-go/freetype/raster.Point composite literal uses unkeyed fields
arc.go:65: code.google.com/p/freetype-go/freetype/raster.Point composite literal uses unkeyed fields
arc.go:67: code.google.com/p/freetype-go/freetype/raster.Point composite literal uses unkeyed fields
path_adder.go:26: code.google.com/p/freetype-go/freetype/raster.Point composite literal uses unkeyed fields
path_adder.go:28: code.google.com/p/freetype-go/freetype/raster.Point composite literal uses unkeyed fields
path_adder.go:40: code.google.com/p/freetype-go/freetype/raster.Point composite literal uses unkeyed fields
path_adder.go:49: code.google.com/p/freetype-go/freetype/raster.Point composite literal uses unkeyed fields
path_adder.go:53: code.google.com/p/freetype-go/freetype/raster.Point composite literal uses unkeyed fields
path_adder.go:56: code.google.com/p/freetype-go/freetype/raster.Point composite literal uses unkeyed fields
path_adder.go:56: code.google.com/p/freetype-go/freetype/raster.Point composite literal uses unkeyed fields
path_adder.go:59: code.google.com/p/freetype-go/freetype/raster.Point composite literal uses unkeyed fields
path_adder.go:59: code.google.com/p/freetype-go/freetype/raster.Point composite literal uses unkeyed fields
path_adder.go:59: code.google.com/p/freetype-go/freetype/raster.Point composite literal uses unkeyed fields
exit status 1
@stanim stanim self-assigned this Jul 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant