Then there's the "design argument": I want juniors to understand that data processing and business operation execution are not "algorithmic recipes" (Do this, wait for that, process that, etc) but a continuous flow of work, and as part of your work you could trigger more work
-
I do think explicit dependencies are worthwhile, and they are on the plan for enkiTS once I get some solid time to implement and test.
FWIW, I checked out EnkiTS and I don't think you need to modify it to accommodate dependencies or continuations. A user can easily create a TaskSetWithContinuation class derived from ITaskSet or build a dependency hierarchy that just calls your scheduler.
-
-
@Manu343726, if you're evaluating it, I would definitely give this a go and write your own derived class to support continuations/onComplete tasks. -
Adding single task continuations should be trivial, but also not that useful since you could also just launch the tasks at the end of your task function, and this doesn't solve the issues mentioned above. Multiple dependencies such as the proposed C++ when_all are trickier.
- Näytä vastaukset
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.