-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Closed
Labels
Description
I've noted that BlockingMultiObserver#blockingGet() wraps and re-throws InterruptedException. This makes hard to recover interrupted state of a thread. The general convention is to either throw IE as is or restore the interrupted state so downstream code could handle it too.
RxJava seem to partially follow this convention, see #147 and
Thread.currentThread().interrupt(); |
Did you consider restoring interrupted state in blocking operations designed for external use, specifically in Completable
, Single
, Maybe
, Observable
blocking*
methods?