Swiftpack.co - muukii/RxFuture as Swift Package

Swiftpack.co is a collection of thousands of indexed Swift packages. Search packages.
See all packages published by muukii.
muukii/RxFuture 5.1.0
🛸A library to provide Future/Promise pattern API that is backed by RxSwift.
⭐️ 5
🕓 1 week ago
.package(url: "https://github.com/muukii/RxFuture.git", from: "5.1.0")


A temporary solution

What's this?

A library to provide Future/Promise pattern API that is backed by RxSwift.

Why do we need this against using Single?

Firstly, Future/Promise pattern fits to return a single result of an asynchronous task.

func doSomething() -> Future<E>

Future/Promise pattern can also do with API of RxSwift only. With using Observable or some PrimitiveSequence.

The problems in this case, First, Observable does not know how many it will be subscribed. So, Observable always should be shared sequence. If it isn't, a task wrapped by Observable will run by each of subscribe. Second, a task wrapped by Observable does not know when starts. It depends on subscribe.

The second case depends on RxSwift. Almost of Observables in RxSwift are cold-observable.

func doSomething() -> Observable<E>

the name of this function says "do something", but actually, "something" will not be done until subscribed.

A below name may be better than above.

func taskToDoSomething() -> Observable<E>

Basically, Future will run a wrapped task immediately. So, I created an object like as Future with RxSwift.

What's the differences with Single<E>?

RxFuture is different with Single. We can say RxFuture runs similar with Combine.Future.
RxFuture and Combine.Future runs their tasks immediately and they caches result until they are deallocated.


Stars: 5
Last commit: 1 week ago
jonrohan Something's broken? Yell at me @ptrpavlik. Praise and feedback (and money) is also welcome.


Swiftpack is being maintained by Petr Pavlik | @ptrpavlik | @swiftpackco | API | Analytics