Book Image

Swift Protocol-Oriented Programming - Fourth Edition

By : Jon Hoffman
Book Image

Swift Protocol-Oriented Programming - Fourth Edition

By: Jon Hoffman

Overview of this book

Protocol-oriented programming is an incredibly powerful concept at the heart of Swift's design. Swift's standard library was developed using POP techniques, generics, and first-class value semantics; therefore, it is important for every Swift developer to understand these core concepts and take advantage of them. The fourth edition of this book is improved and updated to the latest version of the Swift programming language. This book will help you understand what protocol-oriented programming is all about and how it is different from other programming paradigms such as object-oriented programming. This book covers topics such as generics, Copy-On-Write, extensions, and of course protocols. It also demonstrates how to use protocol-oriented programming techniques via real-world use cases. By the end of this book, you will know how to use protocol-oriented programming techniques to build powerful and practical applications.
Table of Contents (11 chapters)

Requirements for the sample code

When we develop applications, we usually have a set of requirements that we need to work toward. Our sample projects in this chapter and the next are no different. The following is a list of requirements for the vehicle types that we will be creating:

  • We will have three categories of vehicles: sea, land, and air. A vehicle can be a member of multiple categories.
  • Vehicles may move or attack when they are on a tile that matches any of the categories they are in.
  • Vehicles will be unable to move to or attack on a tile that does not match any of the categories they are in.
  • When a vehicle's hit points reach zero, the vehicle will be considered incapacitated. We will need to keep all active vehicles in a single array that we can loop through.

For our design in this chapter, we will be demonstrating the design with only a few vehicles, but we know...