Dmitry Vyukov

Which TB functionality does not belong to F? I see logging, erroring and skipping there. Skipping we need. Erroring we need in some form, we can panic, but calling methods...

I agree that functions like SkipNow are less useful than say Skipf. But I think the main question is if we need that compatibility between F and TB or not....

> Execution time The main fuzzing corpus should not be checked into stdlib repo, regardless of if we support multiple corpus locations or not. So long execution time should not...

> I think Dmitry had wondered aloud in another issue if maybe go.mod could help with that problem, but I've observed a large amount of reluctance to put more information...

> Running go test . probably shouldn't dirty your VCS status. This sounds reasonable. I would say a requirement. > That means things like -run with part of a filename...

Yes, let's postpone implementing TB. In the end interfaces are retrofit-able in Go so we don't burn any bridges. The only motivation for implementing TB is sharing code between fuzz...

@tv42 done FTR, the pending PR is https://github.com/dvyukov/go-fuzz/pull/223

Let's please move the discussion of the complex args to #65. There are too many scattered discussions already.

Yes, it's frequently quite hard to understand what exactly happens inside of a fuzzer and why. Minimization is a possible cause, which suggests that if we implement the "corpus rotation"...

Re multi-armed bandit, I think we need to start with some framework that allows to more explicitly distribute interations (time?) across multiple strategies and with statically assigned priorities. The second...