Value and reference semantics

We saw back in Chapter 1, Swift Building Blocks, that certain Swift types behave differently from others, specifically regarding ownership and the mutation of properties. We even defined this difference, saying that classes are reference types, while structs and enums are value types.

Getting ready

In this recipe, we will examine why these types behave differently and the performance implications this entails.

Let's create the model for an app that allows a user to schedule events that they do every day and reminds them when these events should occur.

Therefore, we need to decide how we will model our daily event; the key to this decision is whether we want our event to have reference semantics...