These messages look very terse, to the point that they are probably very hard to understand for someone who is not that familiar with Go.  A Go newbie, who uses Flycheck to check their files, would probably not be able to work from that terse a message to a proper fix easily.  

Is there a way to get more verbose error messages from this tool, to provide better guidance for our users?