-
Notifications
You must be signed in to change notification settings - Fork 7.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix issue #1187 and #1196 #1188
Conversation
Perhaps we should consider putting the "work" as the last (curried) argument.
Would look very nice like this
|
RxJava-pull-requests #1098 FAILURE |
RxJava-pull-requests #1099 FAILURE |
Yep. This Looks better. |
I always try to use that pattern with |
RxJava-pull-requests #1100 FAILURE |
RxJava-pull-requests #1101 FAILURE |
Also fixed #1196 in this PR |
RxJava-pull-requests #1107 FAILURE |
RxJava-pull-requests #1108 FAILURE |
This PR fixed issue #1187.
Although using
(action: => Unit)
will require the following odd codes when somebody wants to useFunction0
directly:I think people rarely use
Function0
directly in Scala.So I chose
(action: => Unit)
finally.schedulerExample4
is an more realistic example for recursive schedule.This PR is a breaking change.