Josh Bleecher Snyder

> Which TB functionality does not belong to F? It seems to me that, of TB: F really needs: `Fatal`, `Fatalf`, `Skip`, `Skipf`. Maybe it also should have: `Log`, `Logf`....

FWIW, I read Russ's comment as saying that testing.F should implement testing.TB, and then proposing a way to achieve that. But I think we should start by implementing it in...

Part of what makes fuzzing effective is a straightforward relationship between the input byte slice and what is done with it. As an example, instrumentation notes when a comparison fails...

Another fuzz.F method pair to consider: `StopCoverage()` and `StartCoverage()`. The idea is that, when called, we would stop/start gathering coverage information. The implementation would probably be that we would swap...

I wish I knew! I’ve observed the same thing and spent some time trying to understand why. I don’t yet. My best theory is that it has to do with...

Somewhat related... I have some mutations implemented locally that are expensive but effective. I’ve been thinking for a while about monitoring coverage and if progress stalls for a while, switch...

Yes, we should document these in the readme. I actually think we shouldn’t display restarts at all, but instead monitor them and print a warning on stderr as needed; the...

> This means that if it's a string, but is actually an integer/float, we should encode it as integer/float if we are going to rely on that type during fuzzing...

> This means that if we have, say int16(42), we should consider we actually have all of int64(42), int32(42), int16(42) and int8(42). Sounds good to me. This significantly increases the...

Thanks, @AlekSi! Very, very much appreciated. I think that we should move if/when two conditions are met: * It is clear that integration into the core go tool won't happen...