Cocoa Design Patterns in Swift

Cocoa Design Patterns
in Swift
@MicheleTitolo

• New language features
• Functional patterns
• Patterns in Swift
• Anti-patterns
What we’ll cover

Tuples group multiple values
into a single compound value.

let http404Error = (404, "Not Found")
println(http404Error.0)

var http200Response: (statusCode: Int, statusText: String,
hasBody: Bool)
http200Response.statusCode = 200
http200Response.statusText = "OK"
http200Response.hasBody = true

You can put any kind
of object in a tuple

Create functions without
declaring type

struct Stack<T> {
var items = [T]()
mutating func push(item: T) {
items.append(item)
}
mutating func pop() -> T {
return items.removeLast()
}
}

“Closures are behaviors
with attached state”
- Peter Norvig

var closure = { (params) -> returnType in
statements
}

var myString: String? = someFucntion()
if let greeting = myString {
println(greeting)
}
else {
println("Not a string")
}

struct Rect {
var origin: Point
var size: Size
}

Structs can have methods, and
conform to protocols

Also can conform
to protocols and have methods

enum Rank: Int {
case Ace = 1
case Two, Three, Four, Five, Six, Seven, Eight, Nine, Ten
case Jack, Queen, King
func description() -> String {
switch self {
case .Ace:
return "ace"
case .Jack:
return "jack"
case .Queen:
return "queen"
case .King:
return "king"
default:
return String(self.toRaw())
}
}
}

func printExcitedly(string: String){
println(string + "!!!!!!!")
}
var excitedFunc = printExcitedly

func printVeryExcitedly(excitedFunction: (String) -> Void,
message: String){
excitedFunction(message.uppercaseString)
}
printVeryExcitedly(printExcitedly, "Hello");

Return functions
from functions

func beExcited(excitementLevel: Int) -> (String) -> Void {
...
}

...because we can pass
functions!

class Car {
let numWheels: Int
let numCylinders: Int
init (numWheels: Int, numCylinders: Int) {
self.numWheels = numWheels
self.numCylinders = numCylinders
}
}
var newCar = Car(numWheels: 4,numCylinders: 4)
var otherCar = Car(numWheels: 4, numCylinders: 6)

protocol Vehicle {
var numWheels: Int {get set}
var numCylinders: Int {get set}
func drive()
}

How do we handle this at
scale?

struct WheelSet {
var wheelSize: Int
var wheelFrictionCoefficient: Float
}
struct BodyType {
var numWheels: Int
var wheels: WheelSet
var wheelBase: Float
}
enum EngineType: Int {
case Automatic, Manual
}
protocol Vehicle {
var body: BodyType {get set}
var transmission: EngineType {get set}
func drive(force: Float)
func turn(speed: Float)
}

Abstract away object
creation and composition

protocol VehicleCreator {
func createVehicle(bodyType: BodyType, engineType: EngineType) -> Vehicle
}
class VehicleFactory: VehicleCreator {
func createVehicle(bodyType: BodyType, engineType: EngineType) -> Vehicle {}
}

protocol VehicleCreator {
func createVehicle(bodyType: BodyType, engineType: EngineType) -> Vehicle
}
class VehicleFactory: VehicleCreator {
}
class MotorcycleFactory: VehicleCreator {
}

class VehicleFactory {
func wheelSetGenerator(wheelSize: Int,
friction: Float) -> WheelSet {
return WheelSet(wheelSize: wheelSize,
wheelFrictionCoefficient: friction)
}
func generateBodyType(wheelCount: Int,
wheelType: WheelSet,
wheelBase: Float) -> (Void) -> BodyType {
func bodyGen() -> BodyType {
return BodyType(numWheels:wheelCount,
wheels:wheelType,
wheelBase:wheelBase)
}
return bodyGen
}
func createVehicle(
bodyGenerator:(wheelCount: Int,
wheelType: WheelSet,
wheelBase: Float) -> BodyType,
transmission: EngineType) -> Vehicle {}
}

let factory: VehicleFactory = VehicleFactory()
let motorcycleWheelSet: WheelSet = factory.wheelSetGenerator(28, friction: 0.5)
let motorcycleBodyGen = factory.generateBodyType(2,
wheelType:motorcycleWheelSet,
wheelBase: 45)
let motorcycle = factory.createVehicle(motorcycleBodyGen, transmission: .Manual)
let electricMotorcycle = factory.createVehicle(motorcycleBodyGen,
transmission: .Auomatic)

Factories in Swift can be
incredibly flexible

A delegate chain
that returns a function

protocol Commander {
func commandSomething(String) -> (Int) -> Dictionary<String, String>
}
class ViewController: {
let delegate: Commander
}

Why is this better
than closures?

We have new ways of
transforming collections

[1,2,3,4].map {
(var number) -> Int in
return number * number
}

var array = [3, 2, 5, 1, 4]
array.sort { $0 < $1 }

let array = [1, 2, 3, 4, 5]
let reversedArray = array.reverse()
// reversedArray = [5, 4, 3, 2, 1]

And of course, this is useful for
more than just math

var vehicles = [suv, motorcycle, electricMotorcycle, car, truck]
var manualVehicles = vehicles.filter {
(var vehicle: Vehicle) -> Vehicle in
return (vehicle.transmission == .Manual)
}
// manualVehicles = [motorcycle, truck]

func meanMedianMode(a: Array<Int>) -> (mean:Int, median:Int, mode:Int) {
var mean = findMean(a)
var median = findMedian(a)
var mode = findMode(a)
return (mean, median, mode)
}

Tuples with names are
incredibly useful

No changes to
handling protocols

This is the slide I was hoping
to put something magical on

class ViewController: UIViewController, UITableViewDataSource {
var tableView: UITableView
func tableView(tableView: UITableView!, cellForRowAtIndexPath indexPath: NSIndexPath!) ->
UITableViewCell! {
var cell : UITableViewCell = tableView.dequeueReusableCellWithIdentifier("Cell") as
UITableViewCell
if (cell == nil) {
cell = UITableViewCell(style: UITableViewCellStyle.Default, reuseIdentifier: "Cell")
}
cell.textLabel.text = "Hello World"
return cell
}
func tableView(tableView: UITableView!, numberOfRowsInSection section: Int) -> Int {
return 1
}
}

Protocols are first class citizens
in Swift, just like in Obj-c

Yes, you can put a tuple in a
tuple

These are temporary data
structures

We have better OO
tools available

Don’t overload default
operators

func decode(json: JSON) -> User? {
return _JSONObject(json) >>> { d in
User.create <^>
d["id"] >>> _JSONInt <*>
d["name"] >>> _JSONString <*>
d["email"] >>> _JSONString
}
}

Operators make code
harder to read

Getting classes from
AnyObject are kind of a pain

Still be explicit when you can

var music: [String: String] = ["AC/DC": "Hells Bells",
"Red Hot Chili Peppers": "Californication"]

But Objective-C, and its
patterns, aren’t going away
anytime soon

More Swift!
• Today 11:30am
Interoperating Swift with Lower Level Code
by Stephan Tramer in Terrace
• Tomorrow 1:45pm
Functional Programming in Swift
by Chris Eidhof in Vail

Resources
• Swift Programming Guide from Apple
• Design Patterns in Dynamic Programming by Peter
Norvig
• Erica Sadun’s many blog posts on Swift
• Functional Programming in Swift, ebook by Objc.io
founders (See Chris’ talk tomorrow!)
• Instance Methods and Curried Functions in Swift by Ole
Begemann

Cocoa Design Patterns in Swift

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (11)

Similar to Cocoa Design Patterns in Swift

Similar to Cocoa Design Patterns in Swift (20)

More from Michele Titolo

More from Michele Titolo (20)

Recently uploaded

Recently uploaded (20)

Cocoa Design Patterns in Swift