Exploring Challenges of Adding Support for Asynchronous/Effect Batches
I'm brainstorming about how to add support for asynchronous/effect batches. The global batchState works great for sync, but I can't see how it could work for async. I'm not even sure there's a way to have async batches with sensible semantics. What would happen if you read an Rx, await some api call, then read it again? It could have a different value unless you somehow snapshotted all values before starting the async process. I think it kinda treads close to STM territory. Perhaps it's just an API issue though, since you could always just defer all your writes until the end of some async process then write them in a synchronous batch. Any ideas @Tim Smart ?
Similar Threads
Was this page helpful?
