// 1
enum DrinkError: ErrorType case NoBeerRemainingError
}
// 2
func drinkWithError() throws if beer.isAvailable{
// party!
} else // 3
throw DrinkError.NoBeerRemainingError
}
}
func tryToDrink{
// 4
do {
try drinkWithError)
} catch {
)
return
There are a few things to highlight here:
- To create an error to throw,simply create an@H_301_45@enumthat derives from@H_301_45@ErrorType.
- You need to use the@H_301_45@throwskeyword to mark any function that can throw an error.
- This throws an error,which will be caught in section 4.
- Instead of@H_301_45@tryblocks,which might be familiar from other languages,you wrap any code that can throw an error in a@H_301_45@doblock. Then,you add the@H_301_45@trykeyword to each function call that could throw an error.
The new Syntax is pretty lightweight and readable. Any API that currently uses@H_301_45@NSErrornow uses this system,so we’ll be seeing a lot of it!
Binding
With Swift 1.2,we lost the “pyramid of doom” and gained the ability to test binding multiple optionals in one line:
@H_502_172@ if let pants = pants,frog = frog // good stuff here!
That works just fine,but the issue for some people is that the “preferred” code path where all the optionals have some value is indented. That means you need to keep looking inside indented code blocks for the mainline part of your code,while the error conditions are outside.
If only there were some way to check that some of the optionals don’t have a value,and then exit early! That’s exactly what Swift 2 offers with its guard statement:
guard = frog // sorry,no frog pants here :[
// at this point,frog and pants are both unwrapped and bound! |
Using@H_301_45@guardmeans you can perform the optional binding (or any other operation,really) and provide a code block in the@H_301_45@elseto run if the condition fails. Then,you can continue on –in this case,the optionals@H_301_45@frogand@H_301_45@pantsare now bound and are no longer optionals in scope.
This should make for much clearer code since@H_301_45@guardlets you specify the state you’re actually expecting rather than checking for the error case.
Note:If your’e still confused about why the
@H_ 301_45@guardstatement is more useful than
@H_ 301_45@if-elsestatements alone,check out Swift team member
Eric Cerney‘s post on the
Swift guard statement.
Protocol Extensions
Object-oriented? Functional? There’s one more to add to the front of the line of what Swift is: a protocol-oriented programming language!
In Swift 1,protocols were like interfaces to specify a set of properties and methods that a class,struct,or enum would then conform to.
Now in Swift 2,you can extend protocols and add default implementations for properties and methods. You can already do this with classes and structs — adding new methods to@H_301_45@Stringor@H_301_45@Array,for example — but adding these to protocols now gives you a much wider reach.
extension CustomStringConvertible var shoutyDescription: String return "\(self.description.uppercaseString)!!!"
let greetings = ["Hello","Hi",26)">"Yo yo yo"]
// prints ["Hello","Hi","Yo yo yo"]
\(greetings.description)")
// prints [HELLO,HI,YO YO YO]!!!
\(greetings.shoutyDescription)") |
Note that the@H_301_45@Printableprotocol is now called@H_301_45@CustomStringConvertible,which most Foundation objects conform to. With protocol extensions,you can extend wide swaths of the system with your own custom functionality. And rather than adding bits of custom code to many classes and structs and enums,you can write one general implementation and have it apply across a set of types.
The Swift team has been busy doing this already —if you’ve ever used@H_301_45@mapor@H_301_45@filterin Swift,you may have thought they would do better asmethodsrather than as global functions. Thanks to the power of protocol extensions,there are a new set of methods on collection types such as@H_301_45@map,55)">filter,55)">indexOf,and more!
let numbers [1,5,217)">6,217)">10,217)">16,217)">42,217)">45// Swift 1
findfiltermap(numbers,{ $0 * 2}),0)">% 3 == 90// Swift 2
numbers.map 2 }.filter }.indexOf() // returns 2 |
Thanks to protocol conformance,your Swift 2 code can be more concise and readable. With the Swift 1 version,you need to look at the calls inside out to understand what’s going on; in the Swift 2 version,the chain of functions is clear.
You’re also leveraging the power of protocol-oriented programming —check out theWWDC session on this topicand keep an eye out for future tutorials and articles here on the site!
Grab Bag
There were a ton of things announced throughout all the sessions,so I want to highlight a few more quick things:
- Objective-C generics– Apple has already started annotating all their Objective-C code so that types in Swift get the correct kind of optionality. That work continues with Objective-C generics,which will give Swift developers better type hinting. If you’re expecting a set of@H_301_45@UITouchobjects or an array of strings,that’s exactly what you’ll get rather than a collection of@H_301_45@AnyObjects.
- Renamed Syntax–@H_301_45@printlnhas left us after only a year; now it’s plain old@H_301_45@printwhich now has a default second boolean argument set to@H_301_45@trueon whether to print a newline or not. With the@H_301_45@dokeyword focused on scope for error handling,do-while loops are nowrepeat-while. Similarly,there are many changes to protocol names such as@H_301_45@Printablebecoming@H_301_45@CustomStringConvertible.
- Migrator– With all these small Syntax changes,how are you going to get your codebase up to date? The Swift 1-to-2 migrator will come to the rescue and help bring things up to the latest standards and Syntax changes. The migrator is even smart enough to update your code to use the new error handling and update your docblock comments to the new style of formatting!
- Open source!–The big news for the nerds is that Swift is going open source when Swift 2 is released in the fall. Likely this will lead to Swift being used for more than just iOS development,which makes it even more important to learn. Plus,it will be a great opportunity to get a look under the hood and even to contribute back and get your name in the Swift compiler commit history. ;]
|
