Book Image

Swift 3 New Features

By : Keith Elliott
Book Image

Swift 3 New Features

By: Keith Elliott

Overview of this book

Since Swift was introduced by Apple in WWDC 2015, it has gone on to become one of the most beloved languages to develop iOS applications with. In the new version, the Swift team aimed to take its adoption to the next level by making it available for new platforms and audiences. This book will very quickly get you up to speed and productive with Swift 3. You will begin by understanding the process of submitting new feature requests for future versions of Swift. Swift 3 allows you to develop and run your applications on a Linux machine. Using this feature, you will write your first Linux application using the debugger in Linux. Using Swift migrator, you will initiate a conversion from Swift 2.2 to Swift 3. Further on, you will learn how to interact with Cocoa libraries when importing Objective C to Swift. You will explore the function and operator changes new to Swift 3, followed by Collection and Closure changes. You will also see the changes in Swift 3 that allow you write tests easier with XCTest and debug your running code better with new formats as well. Finally, you will have a running server written completely in Swift on a Linux box. By the end of the book, you will know everything you need to know to dive into Swift 3 and build successful projects.
Table of Contents (16 chapters)
Swift 3 New Features
About the Author
About the Reviewer
Function and Operator Changes – New Ways to Get Things Done

Unmanaged and UnsafePointer changes

Brace yourself, because we are about to skim the surface of a few types that you may not have seen a lot of and whose names scream, I'll pass on those for the squeamish among you. For the most part, the naming conventions for types in Swift seem approachable and sane to the average developer. However, there is a subset of types that aren't even listed in the main sections of the Swift Programming language document. These are the black sheep types of the language. The ones with names such as Unmanaged, UnsafeMutableRawPointer, and UnsafeBufferPointer. These types just feel unsafe to use. Perhaps, the names are a big hint that you, as the developer, need to take some precautions when using these types. If you develop long enough in Swift, you will eventually come across one of these types. We might as well cover the changes for these types in Swift 3 so that you will be armed with the most current knowledge of how to use the new features when you need them...