Andrea Fioraldi

> why close this? we agreed to move away from libdesyscall for the paper, and the code is not finished

Hey Henri, I will adapt the code in the following days/weeks, I'm quite busy now

@Dominik Maier ***@***.***> yes revert it (in vacation w/o pc), it was a fix by that guy for his usecase, revert it if broken Il ven 16 feb 2024, 17:08...

I don't get this. LLMP TCP etc can coexist, we don't need a new feature

I think the way to go here to avoid code reuse is a macro that define Launcher with different names (CentralizedLauncher, TCPLauncher etc) changing the trait bound to the different...

Also, we want something like "Sync pushing new testcases to the other fuzzer, never get new testcases from them" or viceversa

sending type info is not possible as typeid et similar requires 'static and Input is not, and even if we force Input to be static the type ids may change...

types registries (like inventory, that requires std and it is not compile-time but load-time as it uses constructors) require trait objects. We have a serializable trait objects registry, https://github.com/AFLplusplus/LibAFL/blob/main/libafl/src/bolts/serdeany.rs, but...

> I'm unclear as to why this would need to be static... At no point would this require TypeId. dyn Something forces Somthing to be static

Yes sorry I meant dyn Any, for the downcast