Yeah go-fuzz is an awesome tool, which I've used extensively on some of my own projects.

When writing parsers and compilers it has proven eerily good at identify corner-cases (panics, and infinite loops).

I'm looking forward to trying the new approach out. Anything that makes fuzz-testing easier to configure/maintain and spreads awareness is a good thing in my book.

go-fuzz requires an instrumented binary. It's essentially a forked Go compiler. So I think it's fair to call this a limitation of the language. But I don't see that as a negative. :)