

Xcode 7 will automatically build Swift 2 code in a special “compile for testing” build mode that makes it easier to control visibility from unit tests without making symbols Public. A consequence of this is that many symbols ended up being Public that really were not meant to be. Unit TestingĪ problem with unit testing Swift 1.x code is that Swift 1.x requires you to mark symbols Public to be visible to unit test bundles. Those changes, though, do not apply to functions imported from C and Objective-C APIs.Īdditionally, the model to declare parameter labels has been streamlined by removing the # option, which was used in Swift 1.x to denote an parameter having the same internal and external name.

You can subscribe to receive notifications via RSS.

This InfoQ article is part of the series “ IOS 9 For Developers ”. It comprises five articles that will cover what’s new in iOS 9 SDK, new features in Swift, Objective-C, and developer tools, and Apple’s new bitcode. This series aims at introducing all that is essential for developers to know about building apps for the latest release of Apple’s mobile OS. Along with the new SDK, iOS 9 is also marked by new developer tools to support some of its features, and new releases of Apple’s major programming languages, Swift and Objective-C. Although the new SDK does not introduce as many new or enhanced features as iOS 8, which included more than 4,000 new APIs, it does still provide a wealth of new functionality and enhancements.
