4.x: Improve AsyncSubject by using lock-free methods #510
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 PR changes
AsyncSubject
to be a lock-free implementation by using atomics.Since the observable protocol forbids calling the
OnXXX
methods concurrently, there was no real need for the locked regions and it didn't protect against most races anyway.Some complication is due to the disposability feature thus that explicit state has to be checked and the relevant exceptions thrown.
The observer management has been also replaced by a straight atomic copy-on-write logic so concurrent subscriptions and subscription-termination races are handled without blocking. Note that the original implementation used
ImmutableList.Add
which is by itself also copy-on-write thus this change should not worsen the overhead of tracking a lot of observers while the subject is active.