Skip, SkipLast, Take, TakeLast with time

[akarnokd]

Issue #653

[cloudbees-pull-request-builder]

RxJava-pull-requests #588 SUCCESS
This pull request looks good

[cloudbees-pull-request-builder]

RxJava-pull-requests #589 SUCCESS
This pull request looks good

[cloudbees-pull-request-builder]

RxJava-pull-requests #592 SUCCESS
This pull request looks good

[benjchristensen]

What is the reason for the drain concept? I know it exists in .Net but I don't believe we need this in Java.

I can imagine concern with not wanting a Timer thread to do long-running work, but we don't have that issue with our Scheduler implementations. We always have the time aspects of our schedulers running on separate threads (such as GenericScheduledExecutorService in the case of NewThreadScheduler so we don't block time events.

[akarnokd]

I think it was added to avoid scheduling onNext calls individually but rather emit everything in one go. I haven't found any other places where this kind of overload was present in Rx.NET. Should I remove that overload? Are the other variants okay to stay?

[akarnokd]

I'll resubmit this since it conflicts with master anyway.