3 ms·
you guessed right that this isn't directly useful to my life. all my parallelism is already taken care of by a framework. that said I really like the idea of u
by awinter-py 10y ago
you guessed right that this isn't directly useful to my life. all my parallelism is already taken care of by a framework.
that said I really like the idea of using inner and outer function calls as a hook for spawning and collecting promises. it doesn't only have to be a join on a CPU-bound worker pool; this feels like a cleaner way to abstract IO waits than the yield statements I saw in an early prototype of tulip.
In general, this feels like a clean way to compose any library logic that involves an event loop or execution plan rather than just a function call.