From my understanding Armin's complaint isn't solely that you have to pass it around but the fragmentation of not having a standard way of doing it: >> pass th

From my understanding Armin's complaint isn't solely that you have to pass it around but the fragmentation of not having a standard way of doing it: >> pass the event loop to all coroutines. That appears to be what a part of the community is doing. Giving a coroutine knowledge about what loop is going to schedule it makes it possible for the coroutine to learn about its task. >> alternatively you require that the loop is bound to the thread. That also lets a coroutine learn about that. Ideally support both. Sadly the community is already torn of what to do. Personally I'm not clear on a lot of the minority-use cases that spawns some of this complexity (e.g. when and why would you need to move event loops across threads?) and am quite out of my depth as well.