Book Image

Mastering Swift 5 - Fifth Edition

By : Jon Hoffman
Book Image

Mastering Swift 5 - Fifth Edition

By: Jon Hoffman

Overview of this book

Over the years, the Mastering Swift book has established itself amongst developers as a popular choice as an in-depth and practical guide to the Swift programming language. The latest edition is fully updated and revised to cover the new version: Swift 5. Inside this book, you'll find the key features of Swift 5 easily explained with complete sets of examples. From the basics of the language to popular features such as concurrency, generics, and memory management, this definitive guide will help you develop your expertise and mastery of the Swift language. Mastering Swift 5, Fifth Edition will give you an in-depth knowledge of some of the most sophisticated elements in Swift development, including protocol extensions, error handling, and closures. It will guide you on how to use and apply them in your own projects. Later, you'll see how to leverage the power of protocol-oriented programming to write flexible and easier-to-manage code. You will also see how to add the copy-on-write feature to your custom value types and how to avoid memory management issues caused by strong reference cycles.
Table of Contents (20 chapters)

Dynamic member lookup

Dynamic member lookup enables a call to a property that will be dynamically resolved at runtime. This may not make a lot of sense without seeing an example, so let's look at one. Let's say that we had a structure that represented a baseball team. This structure has a property that represents the city the team was from and another property that represented the nickname of the team. The following code shows this structure:

struct BaseballTeam { 
    let city: String 
    let nickName: String 
} 

In this structure, if we wanted to retrieve the full name of the baseball team, including the city and nickname, we could easily create a method as shown in the following example:

func fullname() -> String { 
    return "\(city) \(nickName)" 
} 

This is how you would do it in most object-oriented programming languages; however, in our code, which...