Add workaround to waitCatch for #14 #15
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This uses the same technique I described in my enclosed-exceptions pull request. I think it would be better to fix this in async itself, so that other packages trying to use async for reliable exception handling get the semantics they're looking for.
simonmar
added a commit
that referenced
this pull request
Aug 4, 2014
Add workaround to waitCatch for #14
|
@simonmar Would it be possible to get a new version of async onto Hackage? |
|
2.0.1.6 just uploaded |
|
Thanks! |
Closed
simonmar
added a commit
that referenced
this pull request
Feb 11, 2019
ttuegel
added a commit
to ttuegel/async
that referenced
this pull request
Mar 2, 2020
simonmar
added a commit
that referenced
this pull request
Mar 5, 2020
waitBoth: Apply the workaround from #15
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This uses the same technique I described in my enclosed-exceptions pull
request. I think it would be better to fix this in async itself, so that
other packages trying to use async for reliable exception handling get
the semantics they're looking for.
Pinging @sol @jcristovao