mackuba

Following the tradition from last year, here's my complete list of all interesting features and updates I could find in Apple's OSes, SDKs and developer tools that were announced at this year's WWDC. This is based on the keynotes, the "What's New In ..." presentations and some others, Apple's release notes, and blog posts and tweets that I came across in the last few weeks.

If for some reason you haven't watched the talks yet, I really recommend watching at least the "State of the Union" and the "What's New In" intros for the platforms you're interested in. The unofficial WWDC Mac app is great way to download the videos and keep track of what you've already watched.

If you're interested, here are my WWDC 2015 notes (might be useful if you're planning to drop support for iOS 8 now and start using some iOS 9 APIs).

---

OSX → macOS 10.12 Sierra

blessingLopes

public protocol Selfie: CustomStringConvertible {}

extension Selfie {

  var description: String {
    let mirror = Mirror(reflecting: self)
    return "\(mirror.subjectType)( \(mirror.children.map({ "\($0!): \($1) "}).joinWithSeparator(", ")))"
   }
}

garohussenjian

// SegueInteractor.swift

// SegueIdentifier enumerates just the segue ID strings in the storyboard. VC's don't switch on this...
private enum SegueIdentifier: String {
    case ShowDetail
}

// SegueInteractor binds closures to segues. VC's switch on this instead!
enum SegueInteractor {
    case PrepareShowDetail((EventEntity) -> Void)

oisdk

import Foundation

protocol Currency { static var sign: String { get } }
enum GBP: Currency { static let sign = "£" }
enum EUR: Currency { static let sign = "€" }
enum USD: Currency { static let sign = "$" }

protocol _Money {
  associatedtype C: Currency
  var amount: NSDecimalNumber { get }

plumhead

extension String {
    func size(withAttributes attrs: [String:AnyObject], constrainedTo box: NSSize) -> NSRect {
        let storage = NSTextStorage(string: self)
        let container = NSTextContainer(containerSize: NSSize(width: box.width, height: box.height))
        let layout = NSLayoutManager()
        layout.addTextContainer(container)
        storage.addLayoutManager(layout)
        storage.addAttributes(attrs, range: NSMakeRange(0, storage.length))
        container.lineFragmentPadding = 0.0
        let _ = layout.glyphRangeForTextContainer(container)

erica

------------
Conformances
------------

protocol AbsoluteValuable
    Conformances:
        Comparable
        IntegerLiteralConvertible
        SignedNumberType

nicklockwood

Thoughts on Swift 2 Errors

When Swift was first announced, I was gratified to see that one of the (few) philosophies that it shared with Objective-C was that exceptions should not be used for control flow, only for highlighting fatal programming errors at development time.

So it came as a surprise to me when Swift 2 brought (What appeared to be) traditional exception handling to the language.

Similarly surprised were the functional Swift programmers, who had put their faith in the Haskell-style approach to error handling, where every function returns an enum (or monad, if you like) containing either a valid result or an error. This seemed like a natural fit for Swift, so why did Apple instead opt for a solution originally designed for clumsy imperative languages?

I'm going to cover three things in this post:

alskipp

-- data structure for RGBA, RGB & CMYK colors
data Color = RGBA Float Float Float Float
           | RGB  Float Float Float
           | CMYK Float Float Float Float
           deriving (Eq, Ord, Show)

-- list of colors
colors = [ RGBA 0.1 0.1 0.5 0.2
         , RGBA 1 1 0 0.9
         , RGB 0.5 0.5 0

marcelofabri

func sumRecursively(numbers: [Int], _ acc:Int = 0) -> Int {
    if let head = numbers.first {
        let tail = Array(dropFirst(numbers))
        return sumRecursively(tail, head + acc)
    } else {
        return acc
    }
}

let myNumbers = [1,2,3,4,5]

andymatuschak

struct User {
	let id: Int
	let name: String
	let email: String?
}

extension User: JSONDecodable {
	static func create(id: Int, name: String, email: String?) -> User {
		return User(id: id, name: name, email: email)
	}