Comment by camgunz

Comment by camgunz a day ago

9 replies

I thought it was the exact same; an event loop in Python is just whatever Io is in Zig, make it a param, get it from an import and a lookup (`import asyncio; loop = asyncio.get_running_loop()`). I might be misunderstanding what you're saying though.

throwawaymaths a day ago

hm maybe. i guess ive only used python in situations where it injects it into amain so i could have been confused. i thought python async was a wrapper around generators, and so the mechanism cant be instantiated in multiple places. i stand corrected.

  • camgunz a day ago

    Oh no you're right it's a pain in the ass and weird. But I think it's the way because there's no good reason to have more than one event loop.

    Also... maybe it started out as generator wrappers? I think I read something that said that.

    • Spivak a day ago

      > no good reason to have more than one event loop

      Per thread—once you start working in multiple threads you have the choice to have one global event loop, which comes at the cost of all async code being effectively serialized as far as threads are concerned*, or one event loop per thread.

      * Which can be fine if your program is mostly not async but you have that one stubborn library. Yay async virality.

      • camgunz a day ago

        I can't say there's no good reason to have per thread event loops, but I think I can say if you do know of one you're suffering a terrible curse. I can only imagine the constraints that would force me to do this.