Josh Bleecher Snyder

I don’t understand. I’ve been using go-fuzz successfully with many Go versions including 1.16. Can you provide steps that I can use to reproduce the issue? Thanks.

I see. That’s unfortunate. How does the PR you sent improve matters?

I'd suggest also filing an issue upstream; 1.18 is probably mostly settled at this point, and if they don't know about an issue, it definitely won't get addressed. :)

Is there a literal 1000000000000000000000000000000000000000000000000000000000000000 in your source code? Is it part of a larger constant expression? Can you share the relevant line of code?

How about in your code's dependencies? We might want to add position information to these errors (cc @thepudds).

@thepudds what do you think?

Thanks! Good find. I have some significant changes queued for int literal collection. I’ll be sure to fix this in the process.

@dvyukov I do. There are a few design decisions to be made relating to effective fuzzing that I don't know the answers to, but you might. I will start a...

There is no principled fix imminent. I’d be happy to look at a workaround PR, although I can’t guarantee it’d be merged. :)

Take all the time you need. :)