Josh Bleecher Snyder

It seems entirely plausible that I used https://github.com/kevinburke/go-bindata by mistake. I had been experimenting with various forks and ideas around that time. (One idea was to use DATA asm instructions...

> I wonder whether using txtar would be better. Or even just a few plain ol' Go const strings. There aren't many of these files, they're short, etc.

Good point. But since go-fuzz will soon be replaced by the standard library, I’m inclined not to change things—and require 1.16—at this point.

(I assume all fuzz functions must be within a single package for this.)

We could do multi-package fuzz functions, but the implementation is a fair bit hairier. Maybe it is worth leaping there, but since I am doing this as a side project,...

Good idea, Dmitry. I’ll start there.

I added the ability to compile multiple fuzz functions at once and then select between them at go-fuzz time. What isn’t implemented is the ability to have go-fuzz run all...

> Question, would it be acceptable to call all fuzz functions from a single parent? You can, but there are downsides: Your corpus and your coverage information gets mixed together....

> IMO, it should require a prefix of of Fuzz, like Test functions do. It does. See `func isFuzzFuncName` in the commit you linked to.

One workaround is to get the cgo/C results by executing another binary, or making an RPC call. It’s ugly, but it does work—go-fuzz has found a bunch of compiler bugs...