>
> Yeah, this is a Watcher, a periodic function that is called to clean up or check something.
> Yes, it’s a very specific pattern. And of course, the Watcher belongs to the service. If the
> service is destroyed, the Watcher should also be stopped.
It’s a Async\Interval, but it behaves entirely like a background fiber (and it can be implemented
using a background fiber as well): what I mean is, it can be treated in the same way as a background
fiber, because it’s an background task that can be spawned by the library in any method: if
await_all was used during construction but not during destruction, it would cause a deadlock
(because it would wait for an uncontrolled background task when exiting the block, according the
proposed functionality of wait_all).
Regards,
Daniil Gentili.