Valentin Huber

> It might make sense to take a good look at how Arbitrary works for different types. https://github.com/rust-fuzz/arbitrary/tree/main/src/foreign/core What are you suggesting with this? Instead of using mapping mutators just...

Ah, that makes sense. Thank you for the suggestion! I'll see what I can do.

So, merging `tuple_list_types` was actually fairly straightforward. Now I'm back to struggling with timelines: ```rust pub trait DefaultMutators { type Type; fn default_mutators() -> Self::Type; } #[derive(Debug, Deserialize, Serialize, SerdeAny,...

I may have another idea, hold on.

So I may have found a solution, but I needed to tear the entire way generics are handled in mapping mutators apart. I've also now introduced the following trait instead...

So I may have found a solution, but I needed to tear the entire way generics are handled in mapping mutators apart. I've also now introduced the following trait instead...

> * We usually use `Std` instead of `Default` everywhere to have a distinction to the rust `Default` trait. I get that for the standard implementations overall, independent of other...

Not yet, no — that's the end goal of this PR. But I need something to derive first, so I'm writing the interface, then a manual implementation in a test...

Still a goal to finish this at some point, but it's not a priority at the moment. Closing this, I'd probably restart anyways because the base changed so much.

Not right now, no. In the future, this may be helpful. Btw: there is no great way right now to do corpus minimization on the fly, right? The cmin examples...