PinkyPromise has retired in success. Its features have been implemented by the Swift language and first party libraries—the best case scenario for long term support.

If you've been a PinkyPromise user, please look into your migration path:

• Results: Use the Swift standard library Result type.
  • But you can often do without Result. An async function can return or throw, so there is now a way to deliver success and failure results with plain syntax and no wrapping type.
• Promises: Use Swift Concurrency.
  • async functions provide regular Promise functionality with greater safety.
  • Where you would have adapted a completion block function by wrapping it in a Promise, first look to see if there is now an async version of the function. If not, use withCheckedContinuation or withCheckedThrowingContinuation. They require the same complete-once contract but offer runtime checks on that condition.
  • Structured concurrency can run many async functions concurrently, like zip and zipArray would do with Promises. Cancellation is available too.
  • Actor isolation can, among other things, require work to happen on the main thread. If you had to pair PinkyPromise with Dispatch, you can migrate away from Dispatch too and get greater safety against data races.
  • The AsyncSequence type lifts for loops into the async world to consume multiple-result tasks, while this library only offered single-result tasks. The Combine framework's AsyncPublisher type bridges from RxSwift-like observable streams to AsyncSequence.
  • Swift Async Algorithms has ways to build on async work tasks in useful ways, like debouncing a sequence.

Thanks for using PinkyPromise!

A tiny Promises library.

PinkyPromise is an implementation of Promises for Swift. It consists of two types:

• Result - A value or error. We use Swift's built in Result Type
• Promise - An operation that produces a Result sometime after it is called. Promises can be composed and sequenced.

With PinkyPromise, you can run complex combinations of asynchronous operations with safe, clean, Swifty code.

• With Carthage: github "willowtreeapps/PinkyPromise"
• With Cocoapods: pod 'PinkyPromise'
• Manually: Copy the files in the Sources folder into your project.

PinkyPromise:

• Is lightweight
• Is tested
• Embraces the Swift language with airtight type system contracts and throw / catch
• Embraces functional style with immutable values and value transformations
• Is a great way for Objective-C programmers to learn functional style in Swift
• Can be extended with your own Promise transformations

PinkyPromise is meant to be a lightweight tool that does a lot of heavy lifting. More elaborate implementations include Result and PromiseKit.

Start with the Examples section below.

We've also written a playground to demonstrate the benefits and usage of PinkyPromise. Please clone the repository and open PinkyPromise.playground in Xcode.

A natural next step beyond Results and Promises is the Observable type. You might use PinkyPromise as a first step toward learning RxSwift, which we recommend.

A Promise is best at running an asynchronous operation that can succeed or fail.

A Result is best at representing a success or failure from such an operation.

The usual asynchronous operation pattern on iOS is a function that takes arguments and a completion block, then begins the work. The completion block will receive an optional value and an optional error when the work completes:

func getString(withArgument argument: String, completion: ((String?, ErrorType?) -> Void)?) {
    …
    if successful {
        completion?(value, nil)
    } else {
        completion?(nil, error)
    }
}

getString(withArgument: "foo") { value, error in
    if let value = value {
        print(value)
    } else {
        print(error)
    }
}

This is a loose contract not guaranteed by the compiler. We have only assumed that error is not nil when value is nil.

Compare with the standard Swift pattern for failable synchronous methods: A function like Data(contentsOf:options:) will either return a value or throw an error, not both, and not neither, and not optionally. This is an airtight contract. But you can't use that pattern in asynchronous calls, because you can only throw backward out of the function you're in, not forward into a completion block.

Here's how you'd write that asynchronous operation with a tighter contract, using Result. The Result is a success or failure. It can be created with return or throw, and inspected with value, which will either return or throw.

func getStringResult(withArgument argument: String, completion: ((Result<String, Error>) -> Void)?) {
    …
    completion?(Result {
        if successful {
            return value
        } else {
            throw error
        }
    })
}
 
getStringResult(withArgument: "foo") { result in
    do {
        print(try result.get())
    } catch {
        print(error)
    }
}

Under the hood, Result<T, Error> is an enum with two cases: .Success(T) and .Failure(Error). It's possible to create a Result using an enum case and inspect it using switch. But since Result represents a returned value or a thrown error, we prefer to use it in the style shown above.

Promises are useful for combining many asynchronous operations into one. To do that, we need to be able to create an asynchronous operation without starting it right away.

To make a new Promise, you create it with a task. A task is a block that itself takes a completion block, usually called fulfill. The Promise runs the task to do its work, and when it's done, the task passes a Result to fulfill. (Hint: The task used to create this Promise is the same as the body of getStringResult(withArgument:).)

func getStringPromise(withArgument argument: String) -> Promise<String> {
    return Promise { fulfill in
        …
        fulfill(Result {
            if successful {
                return value
            } else {
                throw error
            }
        })
    }
}

let stringPromise = getStringPromise(withArgument: "bar")

stringPromise has captured its task, and the task has captured the argument. It is an operation waiting to begin. So with Promises you can create operations and then start them later. You can start them more than once, or not at all.

Next, we ask stringPromise to run by passing a completion block to the call method. call runs the task and routes the Result back to the completion block. When the Promise completes, our completion block will receive the Result, and can get the value or error with try and catch.

stringPromise.call { result in
    do {
        print(try result.get())
    } catch {
        print(error)
    }
}

As we've seen, with Promises, supplying the arguments and supplying the completion block are separate events. The greatest strength of a Promise is that in between those two events, the task-to-be-done exists as an immutable value. And in functional style, immutable values can be transformed and combined.

Here is an example of a complex Promise made of several Promises:

let getFirstThreeChildrenOfObjectWithIDPromise =
    getStringPromise(withArgument: "baz") // Promise<String>
    .flatMap { objectID in
        // String -> Promise<ModelObject>
        Queries.getObjectPromise(withID: objectID)
    }
    .map { object in
        // ModelObject -> [String]
        let childObjectIDs = object.childObjectIDs
        let count = max(3, childObjectIDs.count)
        return childObjectIDs[0..<count]
    }
    .flatMap { childObjectIDs in
        // [String] -> Promise<[ModelObject]>
        zipArray(childObjectIDs.map { childObjectID
            // String -> Promise<ModelObject>
            Queries.getObjectPromise(withID: childObjectID)
        })
    }

getFirstThreeChildrenOfObjectWithIDPromise is a single asynchronous operation that consists of many small operations. It:

1. Tries to get a String for an object ID.
2. If successful, runs an API request for the object with that ID.
3. If successful, collects up to three child IDs from the object.
4. If successful, runs simultaneous requests for each child object, producing an array.
5. Produces either a list of up to three child objects, or an error from any step of the process.

Even though this operation has many steps that depend on prior operations' success, we don't have to coordinate them by writing multiple completion blocks. Instead, we just handle the final result, using the tight contract afforded by Result:

getFirstThreeChildrenOfObjectWithIDPromise.call { [weak self] result in
    do {
        self?.updateViews(withObjects: try result.get())
    } catch {
        self?.showError(error)
    }
}

We intend to keep PinkyPromise fully unit tested.

You can run tests in Xcode, or use bundle exec fastlane run_tests with Fastlane.

We run continuous integration on CircleCI.

• More Promise transformations?

Contributions are welcome. Please see the Contributing guidelines.

PinkyPromise has adopted a code of conduct defined by the Contributor Covenant, the same used by the Swift language and countless other open source software teams.