Book Image

Mastering Swift 3

Book Image

Mastering Swift 3

Overview of this book

Swift is the definitive language of Apple development today. It’s a vital part of any iOS and OS X developer’s skillset, helping them to build the most impressive and popular apps on the App Store—the sort of apps that are essential to iPhone and iPad users every day. With version 3.0, the Swift team have added new features to improve the development experience—making it easier to get the results you want and customers expect. Inside, you’ll find the key features of Swift 3.0 and quickly learn how to use the newest updates to your development advantage. From Objective-C interoperability to ARC, to closures and concurrency, this advanced Swift guide will develop your expertise and make you more fluent in this vital programming language. We give you in-depth knowledge of some of the most sophisticated elements of Swift development including protocol extensions, error-handling, design patterns, and concurrency, and guide you on how to use and apply them in your own projects. You'll see how even the most challenging design patterns and programming techniques can be used to write cleaner code and to build more performant iOS and OS X applications. By the end of this book, you’ll have a handle on effective design patterns and techniques, which means you’ll soon be writing better iOS and OS X applications with a new level of sophistication and control.
Table of Contents (23 chapters)
Mastering Swift 3
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Free Chapter
1
Taking the First Steps with Swift
2
Learning About Variables, Constants, Strings, and Operators

Error handling prior to Swift 2.0


Error handling is the process of responding to and recovering from error conditions within our applications. Prior to Swift 2.0, error reporting followed the same pattern as Objective-C; however, with Swift, we have the added benefit of using optional return values, where returning a nil would indicate an error within the function.

In the simplest form of error handling, the return value from the function would indicate whether it was successful or not. This return value could be something as simple as a boolean true/false value or something more complex such as an enumeration whose values indicated what actually went wrong if the function was unsuccessful. If we needed to report additional information about the error that occurred, we could add an NSError out parameter of the NSErrorPointer type, but this wasn't the easiest approach and these errors tended to be ignored by developers. The following example illustrates how errors were generally handled prior...