Add ResultChannel class and fix multiple continuation calls for AwaitObservable #30
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.
The previous implementation of Async.AwaitObservable fails for hot observables (which immediately call the OnNext event, potentially multiple times, on subscription). This issue is fixed here by introducing ResultChannel<'T> which can be used to post an result and await it asynchronously elsewhere. Also copied across some unit tests for AwaitObservable from the fsharpx project which are now passing reliably.