Naja Melan

> One thing that might be a problem from our side is that we need to be able to have up to two wakers per read/write operation True, I forgot...

Just wanted to mention that stjepang also released async-compat, but unfortunately it doesnt work for tokio 0.3 and it seems to always load tokio with the rt feature... also might...

So do you have to specifically add a binary target to lib crates right now? When not running binary, almost my entire lib get's optimized away because it doesn't get...

If I understand well you want to be able to wrap `std::thread::Handle` in `JoinHandle` so it can be used the same way. I am in favor of the feature. I...

> The idea is to pass runtimes as generic arguments, instead of variables, to avoid unnecessary dynamic dispatch. Passing variables does not cause dynamic dispatch. So where the executor needs...

Ok, I understand what you mean now. Let me hopefully help you forward a bit: > I have to write > > ```rust > fn foo(exec: T) {} > ```...

> then every addition of `spawn_handle` is a breaking change Not really, as there isn't any known implementation of the trait that can spawn some types and not others. Maybe...

Yes, I see if you do it like that it can be a breaking change. I will clarify this issue in the documentation. However you can avoid it: ```rust //...

> What if I want to spawn_handle this? You need `SpawnHandle< Pin >` async_executors used to have the not object safe traits. They were removed in d9a5fe54a63fe03598c2e14674c143ff78253f82 because it creates...

I think the solution here is to implement `agnostik::Executor` behind a feature flag. That way we bring a non- object safe, non generic spawn trait back without having to maintain...