True
-
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.
I agree w/ this. Continuations have proven to me to only be useful in rare cases. Things like async graphics, network, or IO callbacks are reasonable candidates. But in those cases a simple callback is usually sufficient.
-
-
I used to use continuations more, but it was because the codebase I worked with was fairly OOP and didn't lend itself to tasks already. Continuations were a reasonable bandaid for bad architecture. With good architecture, continuations/coroutines are not that useful.
Kiitos. Käytämme tätä aikajanasi parantamiseen. KumoaKumoa
-
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.