Remove intrinsics usage in RibCoroutineWorker
#627
Merged
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.
Currently, we need to build both
bindJob
andunbindJob
synchronously (CoroutineScope.bind
is not suspending and must return a handle with both jobs).In order to synchronously get an instance of
bindJob
, we start theunbindJob
coroutine undispatched (bindJob
is a child ofunbindJob
, so we need an instance ofunbindJob
to create an instance ofbindJob
).This commit changes dispatching logic to a much simpler one that does not require usage of intrinsics: after saving
bindJob
, we properly dispatch in a cancellable way by simplylaunch
ing a new coroutine.