Change scheduler factory to care about loopers, not handlers.

[JakeWharton]

A Looper is the currency of Android-specific work scheduling that we should be exposing. Handler is only a helper through which we access the Looper.

[dlew]

If we're going to another major revision for the next release (2.x), why not just remove it entirely?

[JakeWharton]

Next is 1.2. I don't see a reason to do a major release for it and having
major versions out of sync with RxJava is going to be a mess.

On Mon, May 2, 2016, 9:14 AM Daniel Lew notifications@github.com wrote:

In rxandroid/src/main/java/rx/android/schedulers/HandlerScheduler.java
#282 (comment):

-/** A {@link Scheduler} backed by a {@link Handler}. */
-public final class HandlerScheduler extends Scheduler {

• /* Create a {@link Scheduler} which uses {@code handler} to execute actions. /
  +/
• * A {@link Scheduler} backed by a {@link Handler}.
• * @deprecated Use {@link AndroidSchedulers#from(Looper)}.
• */
  +@deprecated

If we're going to another major revision for the next release (2.x), why
not just remove it entirely?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/ReactiveX/RxAndroid/pull/282/files/0bb9b4e63f5560ca238233f1c4d692d9bc8b5ba0#r61736328

[dlew]

LGTM besides the question of whether to deprecate or remove.

[JakeWharton]

I filed the 2.x issues for the hypothetical future of what needs done for RxJava 2.0–should it ever happen.

[dlew]

Ah, okay, makes sense. In that case deprecation is good.