Voit lisätä twiitteihisi sijainnin, esimerkiksi kaupungin tai tarkemman paikan, verkosta ja kolmannen osapuolen sovellusten kautta. Halutessasi voit poistaa twiittisi sijaintihistorian myöhemmin. Lue lisää
Your application “loop” is done by the tail task scheduling the head task again. This sort of looping is rarely addressed. Yeah we get parallel loops. Those aren’t the challenging part. Those are “embarrassingly” easy.
We need to talk about the entire application being a parallel/concurrent application, starting from your entry point.
Oh good finally someone that sees the problem. Main should initialize the task scheduler, run a task to fire up the system (say initialize db and tcp server) and from there everything is event driven
I have implemented this in a toy OS. It works, but your application is more complicated for it. Soon will retry with c++20 coroutines. https://github.com/dascandy/rodvin_async/blob/master/kernel/src/common/Shell.cpp … - the shell as async program
If you're at the meet the speakers dinner tonight I'd love to chat about this kind of thing
Yes, using lock, wait and get are bugs in an async app. Except when maintaining an invariant for some existing code dependency. Such as preventing main from exiting until the async graph completes. I would love to have an async entry point for c++ programs. It needs a paper.
I already started a library that shores up a basic scheduler and requires a taskMain() implementation. I’ll hopefully post it to GitHub for others to experiment.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.
