Add demo code to assert that the throttleFirst does not switch thread.
#8
Conversation
This file contains hidden or 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
TonyTangAndroid
force-pushed
the
throttle_first
branch
from
a6f22e8 to
254b89f
Compare
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.
As it is demonstrated here, item through
throttleFirstwill remain to be the upstream threadmainwhile item throughthrottleLastwill be switched to theRxComputationThreadPool-2. This comes to me as a surprise, which almost results in incidents in PROD. Hence, I am creating this dedicated pull request to highlight the difference and carve those subtle difference into memory.