Book Image

Hands-On Design Patterns with Swift

By : Florent Vilmart, Giordano Scalzo, Sergio De Simone
Book Image

Hands-On Design Patterns with Swift

By: Florent Vilmart, Giordano Scalzo, Sergio De Simone

Overview of this book

Swift keeps gaining traction not only amongst Apple developers but also as a server-side language. This book demonstrates how to apply design patterns and best practices in real-life situations, whether that's for new or already existing projects. You’ll begin with a quick refresher on Swift, the compiler, the standard library, and the foundation, followed by the Cocoa design patterns – the ones at the core of many cocoa libraries – to follow up with the creational, structural, and behavioral patterns as defined by the GoF. You'll get acquainted with application architecture, as well as the most popular architectural design patterns, such as MVC and MVVM, and learn to use them in the context of Swift. In addition, you’ll walk through dependency injection and functional reactive programming. Special emphasis will be given to techniques to handle concurrency, including callbacks, futures and promises, and reactive programming. These techniques will help you adopt a test-driven approach to your workflow in order to use Swift Package Manager and integrate the framework into the original code base, along with Unit and UI testing. By the end of the book, you'll be able to build applications that are scalable, faster, and easier to maintain.
Table of Contents (22 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

Futures and promises


Futures and promises are terms that are used somewhat interchangeably to refer to abstractions representing the idea of a proxy to a value that will be known at some future time. In other words, futures and promises allow you to create objects that encapsulate asynchronous tasks and their result, and use them without waiting for the asynchronous task to finish, as long as you do not need to access the result of that task. When you need to access the task result, either the task has already completed, in which case you can use it without delay; otherwise, you will need to delay the code that wants to use that result until it becomes available. Strictly speaking, a way to differentiate between futures and promises is to say that a future represents a read-only value that may be available or not, while a promise represents the function that is responsible to set that value at some point in time. Thus, in actual fact, futures and promises are two sides of the same coin....