Valentin Huber

Yes, the corpus will contain everything, of course. But it isn't written to disk, so when I kill the fuzzer, I lose everything but the metadata (found in the `.metadata`...

Ah, I see, seems like I missed something. If I understand correctly, the input content is serialised and written to disk in this method on `Input`, to the file associated...

I guess I could also just implement this for my input, so a global option may not be strictly necessary, but it would still be nice, just for consistency.

Related question: All input types in the repo (at least as far as I can see) generate their testcase names (`fn generate_name(&self, id: Option) -> String;` on `Input`) the exact...

Yes, this kind of does what I would want it to do, but 1. It also serialises corpus, not just solutions (and returns an error if passed something like `/dev/null`)...

That is a fair point. It may however be hard to implement: 1. It'd need some form of synchronisation across clients since they may not run in the same memory...

Even just implementing the bare minimum of this however seems like a lot of work, and I don't have the capacity to do so at the moment. There is still...

> There is still a point to be made that a macro that just implements Named as follows is progress, since it removes code duplication and we decouple the implementation...

> I think we'd want to create a `self.name` with name being `MyNamedThing` if an atomic counter is 0, and `MyNamedThing2` if the conuter is > 0 That would be...

The current problem I'm running into is that the types of the *combined* mutators have to be specified in the macro — generics don't seem to work or at least...