Dmitry Vyukov

I agree restarts is not very useful as is. Cover percent is quite hard to do in a meaningful way. Ideally we need to understand what's potentially coverable and use...

> The current design converts int literals to strings during go-fuzz-build. I'd like to change that, so that the metadata json contains strings and ints, and do the int-to-string conversion...

> The current design encodes ints in the smallest number of bytes possible. Why can it increase chances of matching the underlying structure of the program? I think we should...

> Sounds good to me. This significantly increases the number of literals, but that's ok. I think we should not put them all into the file. There is no point....

> > 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...

I am not sure if this literal collection is a good idea at all. The alternative would be to extract constants from comparison operations at runtime. And this way we...

Thanks! That's definitely better than a private repo. So if we name the repo go-fuzz and have the command sub-dir go-fuzz, that will be `github.com/go-fuzz/go-fuzz/go-fuzz`. We need to go-fuzz deeper!...

Any suggestions on how to better move the code? Just pull from my repo and push there? Any caveats with this?

Also @josharian @thepudds what do you think about moving go-fuzz to the new location? Is it worth it?

Fair enough.