Tv

Nevermind, I didn't run `init`. Retitling to ask for better docs and error message.

A second, I think related, issue is that the types package version shifts over time. I just had a build fail because my lock file had `https://esm.sh/v86/@types/[email protected]/global.d.ts` etc where what...

I wonder if it would be possible to look at the random values `testing/quick` `Config.Values` consumes and adjust those for mutation.

@dvyukov So testing/quick is based on this idea of generating a random complex value, and feeding it either to a `func(....) bool` or to two functions and comparing their return...

Only semi-related but I figured I should record this here for interested parties. Earlier discussion here has brought up the idea of using the fuzz input `[]byte` as a command...

https://github.com/mschoch/smat is a library that essentially converts the `[]byte` from go-fuzz into state machine transitions, where the transition can call methods of the system under test. Interesting. Doesn't seem to...

@dvyukov https://github.com/mschoch/smat/issues/2 looks like the right issue for passing fuzz data []byte to actions. And yes smat seems a bit too simplistic currently, but still, it's interesting to see these...

> For fuzzing-based approach, while explicit generators are not required, [5, 10] constraint should still appear in the test: A big part of the point of fuzzing, from the security...

https://github.com/dvyukov/go-fuzz/issues/218#issuecomment-471690355 sounds like #65 all over again. Could someone please retitle this bug to clarify it's about the `fuzz.F` part, and not "objects" as in complex inputs and not []byte?...

If you use github repo transfers, it breaks all users of the old import path (that don't have it cached already). But I'm in favor of "stdlib or bust".