Christopher Allan Webber <cweb...@dustycloud.org> skribis: > One interesting change from when this was defined last year and this > year is that the "extensible event loop" one has some candidates to pick > from, via guile a-sync, fibers, and 8sync. > > However using any of those would require Shepherd being pinned to Guile > 2.2. Maybe not a problem; it could be a branch, and Guile 2.2 stable > looks not so far away.
Yes, I think it’d be reasonable to have Shepherd rely on 2.2. In fact, we should start moving all of our infrastructure to 2.2. There are still a couple of issues to be addressed I think, but now’s the time to explore. Ludo’.
