Document the new Completable Observable-like variant

[DavidMGross]

It's still being discussed, but it seems like they're leaning toward adding this operator under some name or other to 1.x. See ReactiveX/RxJava#3443

[DavidMGross]

See also: ReactiveX/RxJava#3444 (Completable)

[DavidMGross]

See also: ReactiveX/RxJava#3567 (toCompletable / Completable.fromObservable)

[DavidMGross]

See also: ReactiveX/RxJava#3568 (Completable.doAfterTerminate)

[DavidMGross]

See also:

• Implemented Completable#andThen(Observable) RxJava#3570 (Completable.andThen/endWith)
• 1.x: Add Completable.andThen(Single) RxJava#3799 (Completable.andThen(Single))
• Request: Completable.andThen(Completable) RxJava#3947, Add Completable.andThen(Completable), deprecate endWith() RxJava#3948 (Completable.andThen(Completable)) - deprecates Completable.endWith

[DavidMGross]

See also: ReactiveX/RxJava#3580 (Completable review)

[DavidMGross]

See also: ReactiveX/RxJava#3701 (change name of doOnComplete to doOnCompleted)

[DavidMGross]

See also: ReactiveX/RxJava#3706 (lifecycle of Singles and Completables compared to Observables)

[DavidMGross]

From the RxJava 1.1.1 release notes:

What is this Completable class?

We can think of a Completable object as a stripped version of Observable where only the terminal events, onError and onCompleted are ever emitted; they may look like an Observable.empty() typified in a concrete class but unlike empty(), Completable is an active class. Completable mandates side effects when subscribed to and it is its main purpose indeed. Completable contains some deferred computation with side effects and only notifies about the success or failure of such computation.

Similar to Single, the Completable behavior can be emulated with Observable<?> to some extent, but many API designers think codifying the valuelessness in a separate type is more expressive than messing with wildcards (and usually type-variance problems) in an Observable chain.

Completable doesn't stream a single value, therefore, it doesn't need backpressure, simplifying the internal structure from one perspective, however, optimizing these internals requires more lock-free atomics knowledge in some respect.

Hello World!

Let's see how one can build a (side-effecting) Hello World Completable:

Completable.fromAction(() -> System.out.println("Hello World!"))
.subscribe();

Quite straightforward. We have a set of fromXXX method which can take many sources: Action, Callable, Single and even Observable (stripping any values generated by the latter 3 of course). On the receiving end, we have the usual subscribe capabilities: empty, lambdas for the terminal events, a rx.Subscriber and a rx.Completable.CompletableSubscriber, the main intended receiver for Completables.

Further reading

• The new Completable API - part 1 - http://akarnokd.blogspot.hu/2015/12/the-new-completable-api-part-1.html
• The new Completable API - part 2 - http://akarnokd.blogspot.hu/2015/12/the-new-completable-api-part-2-final.html

[DavidMGross]

See also: ReactiveX/RxJava#3730 (Completable.andThen)

[DavidMGross]

See also: ReactiveX/RxKotlin#48

[DavidMGross]

See also:

• http://akarnokd.blogspot.hu/2015/12/the-new-completable-api-part-1.html
• http://akarnokd.blogspot.hu/2015/12/the-new-completable-api-part-2-final.html