Async today is one thread, one result. That's fine for a single fetch, but a chat client keeps a socket open, and things like tailing a file or reading a child process need a steady stream of messages.
Some way for a background task to keep pushing messages into update (a subscription, or a perform that yields more than once) would cover those. Could sit next to every conceptually.
Async today is one thread, one result. That's fine for a single fetch, but a chat client keeps a socket open, and things like tailing a file or reading a child process need a steady stream of messages.
Some way for a background task to keep pushing messages into update (a subscription, or a perform that yields more than once) would cover those. Could sit next to
everyconceptually.