Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Swift 5.3

You're reading from   Mastering Swift 5.3 Upgrade your knowledge and become an expert in the latest version of the Swift programming language

Arrow left icon
Product type Paperback
Published in Nov 2020
Publisher Packt
ISBN-13 9781800562158
Length 418 pages
Edition 6th Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Jon Hoffman Jon Hoffman
Author Profile Icon Jon Hoffman
Jon Hoffman
Arrow right icon
View More author details
Toc

Table of Contents (23) Chapters Close

Preface 1. Taking the First Steps with Swift 2. Swift Documentation and Installing Swift FREE CHAPTER 3. Learning about Variables, Constants, Strings, and Operators 4. Optional Types 5. Using Swift Collections 6. Control Flow 7. Functions 8. Classes, Structures, and Protocols 9. Protocols and Protocol Extensions 10. Protocol-Oriented Design 11. Generics 12. Error Handling and Availability 13. Custom Subscripting 14. Working with Closures 15. Advanced and Custom Operators 16. Concurrency and Parallelism in Swift 17. Custom Value Types 18. Memory Management 19. Swift Formatting and Style Guide 20. Adopting Design Patterns in Swift 21. Other Books You May Enjoy
22. Index

Native error handling

Languages such as Java and C# generally refer to the error handling process as exception handling. Within the Swift documentation, Apple refers to this process as error handling. While on the outside, Java and C# exception handling may look somewhat similar to Swift's error handling, there are some significant differences that those familiar with exception handling in other languages will notice throughout this chapter.

Representing errors

Before we can really understand how error handling works in Swift, we must see how we can represent an error. In Swift, errors are represented by values of types that conform to the Error protocol. Swift's enumerations are very well suited to modeling error conditions because we generally have a finite number of error conditions to represent.

Let's look at how we would use an enumeration to represent an error. For this, we will define a fictitious error named MyError with three error conditions, Minor...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at AU $24.99/month. Cancel anytime