This is working as designed. Why do you think it is a bug? go generate expects a go:generate comment to be a normal line comment ending at a newline.

Where is that expectation documented? I don't see that it's a necessary or useful requirement, and it's confusing to encounter in the wild.

I have a small patch to fix this ready (once I sort out CLA concerns with my employer). When an EOF is encountered, the generate comment has been read into a buffer. All it needs is a '\n' appended to it to parse and exec, but the current implementation returns io.ErrUnexpectedEOF instead.

I forgot to mention when I filed this issue, I'm not the first person to run into this. See #18066.

Let's just define go generate as requiring a full line comment ending in a newline, and move on.

(If you want to send a very short doc change, we can consider it.)

The only documentation I'm aware of is here: https://golang.org/pkg/cmd/go/internal/generate/

As someone who supports multiple generators for a number of other developers, this is an error I'm likely to be dealing with again. My users are unlikely to be viewing the godocs for that internal package.

In my opinion, if go fmt doesn't force newlines at the end of files (#1178), then go generate shouldn't require them.

I suppose this issue doesn't matter. It's small and the fix is trivial and I'll post it up for review as soon as my employer allows me to.

I think you are misreading #1178. gofmt does ensure that a Go file ends with a newline.

> echo -e -n 'package main\n//go:generate true' > gen.go
> cat -ve gen.go
package main$
//go:generate true> gofmt -w gen.go
> cat -ve gen.go
package main$
$
//go:generate true$

Ah, my mistake. I guess my colleague who encountered this must not have integrated go fmt with GoLand in the way I expected.