| class DelayedBlockOperation: NSOperation { | |
| private var delay: NSTimeInterval = 0 | |
| private var block: (() -> Void)? = nil | |
| private var queue: dispatch_queue_t = dispatch_get_main_queue() | |
| override var asynchronous: Bool { return true } | |
| override var executing : Bool { | |
| get { return _executing } | |
| set { | |
| willChangeValueForKey("isExecuting") |
| import Alamofire | |
| import Foundation | |
| import enum Result.Result | |
| extension Alamofire.Result { | |
| func toStandard() -> Result<Value, Error> { | |
| switch(self) { | |
| case Alamofire.Result.Success(let value) : return Result.Success(value) | |
| case Alamofire.Result.Failure(let error) : return Result.Failure(error) | |
| } |
| #!/usr/bin/sudo sh | |
| ## ruby_revealer.sh -- decrypt obfuscated GHE .rb files. 2.0.0 to 2.3.1+. | |
| ## From `strings ruby_concealer.so`: | |
| ## | |
| ## > This obfuscation is intended to discourage GitHub Enterprise customers | |
| ## > from making modifications to the VM. | |
| ## | |
| ## Well, good, as long as its not intended to discourage *me* from doing this! |
| // | |
| // ArrayDiff.swift | |
| // | |
| // Created by Frank A. Krueger on 6/30/15. | |
| // Copyright © 2015 Krueger Systems, Inc. All rights reserved. | |
| // License: MIT http://opensource.org/licenses/MIT | |
| // | |
| import Foundation |
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:
PS: If you liked this talk or like this concept, let's chat about iOS development at Stitch Fix! #shamelessplug
Speaker: David Abrahams. (Tech lead for Swift standard library)
"Crusty" is an old-school programmer who doesn't trust IDE's, debuggers, programming fads. He's cynical, grumpy.
OOP has been around since the 1970's. It's not actually new.
Classes are Awesome
| #!/bin/bash -e | |
| # | |
| # package-ipa.sh | |
| # | |
| # Bundles an iOS app correctly, using the same directory structure that Xcode does when using the export functionality. | |
| # | |
| xcarchive="$1" | |
| output_ipa="$2" |
2015-01-29 Unofficial Relay FAQ
Compilation of questions and answers about Relay from React.js Conf.
Disclaimer: I work on Relay at Facebook. Relay is a complex system on which we're iterating aggressively. I'll do my best here to provide accurate, useful answers, but the details are subject to change. I may also be wrong. Feedback and additional questions are welcome.
Relay is a new framework from Facebook that provides data-fetching functionality for React applications. It was announced at React.js Conf (January 2015).