Hi, Just a reminder that Go is an open source project. Although changing go:generate probably isn't going to happen, your comment about lint not catching the issue seemed reasonable to me. So I went ahead and implemented it and created a pull request:
https://github.com/golang/lint/pull/291 - Caleb On Saturday, April 29, 2017 at 7:33:20 AM UTC-4, mhh...@gmail.com wrote: > > Hi, > > just a note about the //go:gen comment. > > If there is a space in front of go:gen, it won t work, this, > // go:gen... > > I did not check, but i bet 100 boxes there s already a rule about that. > Clear crystal. > > Still, there is no warning about that in vet/lint, > so for a beginner, > assuming he got them installed, and he is using both of them, > he will still fail and stubble in front of this situation. > > If he is not using any of them, well... dead end. > > And even for someone who did that in the past, > me?, > it is highly frustrating (back to un-typed/weak languages problem... there > s a mistake, where the **** is it???). > > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
