You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The purpose of this abstraction is passing in transformer stacks on top of IO in the negative position, as in:
async::MonadUnliftIOm=>ma->m (Asynca)
What do you think of it? Assuming it is a good abstraction (I happen to think so but as far as I can tell the community is undecided), for organizational purposes, it would be great if async could pick up an unliftio-core dependency, then unliftio can stop mirroring the async API.
Thanks :)
The text was updated successfully, but these errors were encountered:
Here is what
unliftio
has made of theasync
API:https://hackage.haskell.org/package/unliftio-0.2.7.0/docs/UnliftIO-Async.html
The purpose of this abstraction is passing in transformer stacks on top of IO in the negative position, as in:
What do you think of it? Assuming it is a good abstraction (I happen to think so but as far as I can tell the community is undecided), for organizational purposes, it would be great if
async
could pick up anunliftio-core
dependency, thenunliftio
can stop mirroring theasync
API.Thanks :)
The text was updated successfully, but these errors were encountered: