What is the exact command that you run? What is the exact error that you see?

Note that we are likely to need a small test case in order to fix this. Unfortunate experience shows that it is very hard to recreate a specific problem from a text description.

@monotrememan42 go generate does not seem to parse go source files.

Do your go generate lines (the magic comments) invoke, for example, stringer or any other tool that needs the package to be compiled?

Sometimes it might help to "reset" the parser.go file before doing other things, like

//go:generate echo "package foo" > parser.go
//...
//go:generate go tool yacc -o parser.go parser.y

or

// Start with the last known good parser.go
//go:generate git checkout -f parser.go
//...
//go:generate go tool yacc -o parser.go parser.y

the first few lines of the source file are

//go:generate nex -p Parse -e -o ../../gen/rivegen/lexer.go lexer.nex
//go:generate go tool yacc -p Parse -o ../../gen/rivegen/parse.go parse.y
//go:generate mv y.output ../../gen/rivegen

package rive

i am working on getting a small reproducible example for you; i think i can do it in 2-3 files.
i’ll send a zipped tar file. when i do.

On Jul 9, 2016, at 6:29 AM, cznic notifications@github.com wrote:

@monotrememan42 https://github.com/monotrememan42 go generate does not seem https://github.com/golang/go/blob/57e459e02b4b01567f92542f92cd9afde209e193/src/cmd/go/generate.go to parse go source files.

Do your go generate lines (the magic comments) invoke, for example, stringer or any other tool that needs the package to be compiled?

Sometimes it might help to "reset" the parser.go file before doing other things, like

//go:generate echo "package foo" > parser.go
//...
//go:generate go tool yacc -o parser.go parser.y
or

// Start with the last known good parser.go
//go:generate git checkout -f parser.go
//...
//go:generate go tool yacc -o parser.go parser.y
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #16307 (comment), or mute the thread https://github.com/notifications/unsubscribe/AJ8JQKZFTffF4NsrUhW4I2eRgwdOImRGks5qT6IsgaJpZM4JId2b.

attached is a small tar file that contains a reproducible example.
there is a script.out file that shows the bug.
sorry i did not include this originally.

andrew

On Jul 8, 2016, at 6:36 PM, Ian Lance Taylor notifications@github.com wrote:

Note that we are likely to need a small test case in order to fix this. Unfortunate experience shows that it is very hard to recreate a specific problem from a text description.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #16307 (comment), or mute the thread https://github.com/notifications/unsubscribe/AJ8JQGaHjT2gexzinDdo2BxDoYP1b9-Aks5qTvsAgaJpZM4JId2b.

did the attached tar file make it? i don't see it here. i'll attach it again just in case.
ohhh, stupid system doesn't support tar but doesn't tell you (when submitting by email).
lovely. here is the same stuff in a zip file.
go16307.zip

i added the test case to reproduce

On Jul 8, 2016, at 6:36 PM, Ian Lance Taylor notifications@github.com wrote:

Note that we are likely to need a small test case in order to fix this. Unfortunate experience shows that it is very hard to recreate a specific problem from a text description.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #16307 (comment), or mute the thread https://github.com/notifications/unsubscribe/AJ8JQGaHjT2gexzinDdo2BxDoYP1b9-Aks5qTvsAgaJpZM4JId2b.

i'm not trying to annoy anyone, but i wanted to ensure someone had gotten the test cases etc. can someone please speak to that? thanks.

With some modifications I was able to reproduce the problem. I didn't investigate more. I'd look for go/types interfering when go generate is invoked, shooting in the dark, of course.

CL https://golang.org/cl/31659 mentions this issue.