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
I often need to run some important background task which I don't have to wait on and should be cancelled when I'm done.
However, it should interrupt me if it fails.
I've often needed it when writing tests and have been bitten by using withAsync bg (const fg) and having issues with the background task silently failing.
One possible pattern is to remember to always use link in these cases, but link turns synchronous exceptions into asynchronous ones which is a bit weird and not the most ergonomic pattern.
How about having something like the following? Would make link unnecessary for spawning threads you don't need to wait on.
withAsyncThrow::IOa->IOb->IOb
withAsyncThrow left right =
withAsync left $\l ->
withAsync right $\r ->do
e <- waitEither l r
case e ofLeft _ -> wait r
Right v ->return v
Might need a better name (withConcurrent?) but others seem to have come across this need in the past too #128
The text was updated successfully, but these errors were encountered:
Here, importantBackgroundTask will run in a separate thread, propagate any exception if it fails, and will automatically be cancelled at the end of the ... block if it's still running.
I often need to run some important background task which I don't have to wait on and should be cancelled when I'm done.
However, it should interrupt me if it fails.
I've often needed it when writing tests and have been bitten by using
withAsync bg (const fg)
and having issues with the background task silently failing.One possible pattern is to remember to always use
link
in these cases, butlink
turns synchronous exceptions into asynchronous ones which is a bit weird and not the most ergonomic pattern.How about having something like the following? Would make
link
unnecessary for spawning threads you don't need to wait on.Might need a better name (
withConcurrent
?) but others seem to have come across this need in the past too #128The text was updated successfully, but these errors were encountered: