| //: Playground - noun: a place where code can play | |
| import UIKit | |
| //Most precise time keeper | |
| // for more information on the benchmarks go to www.kandelvijaya.com | |
| func timeBlockWithMach(_ block: () -> Void) -> TimeInterval { | |
| var info = mach_timebase_info() | |
| guard mach_timebase_info(&info) == KERN_SUCCESS else { return -1 } |
Picking the right architecture = Picking the right battles + Managing trade-offs
Wil Turner, Brook Callhan: Speakers
##3 Main components/concepts that enable UI Testing:##
Not: Mart 2016 itibariyle aşağıdaki ilan geçersizdir. Şu an için açık pozisyon bulunmamaktadır.
Availability and quality of developer tools are an important factor in the success of a programming language. C/C++ has remained dominant in the systems space in part because of the huge number of tools tailored to these lanaguages. Succesful modern languages have had excellent tool support (Java in particular, Scala, Javascript, etc.). Finally, LLVM has been successful in part because it is much easier to extend than GCC. So far, Rust has done pretty well with developer tools, we have a compiler which produces good quality code in reasonable time, good support for debug symbols which lets us leverage C++/lanaguge agnostic tools such as debuggers, profilers, etc., there are also syntax highlighting, cross-reference, code completion, and documentation tools.
In this document I want to layout what Rust tools exist and where to find them, highlight opportunities for tool developement in the short and long term, and start a discussion about where to focus our time an
| // | |
| // CollectionViewDataSource.swift | |
| // | |
| // Created by Bill Richards on 10/1/14. | |
| // Copyright (c) 2014 Bill Richards. All rights reserved. | |
| // | |
| import Foundation | |
| typealias CollectionViewCellConfigureBlock = (cell:UICollectionViewCell, item:AnyObject?) -> () |
| import Cocoa | |
| // Only needed until we have class variables | |
| var __SwizzleSayHello = { (who:String) -> String in | |
| return "Hello, \(who)" | |
| } | |
| class Swizzle { | |
| //Only needed until we have class variables | |
| class var _sayHello : (String)->String { get{ return __SwizzleSayHello } set (swizzle) {__SwizzleSayHello = swizzle} } |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
| import Cocoa | |
| class AppDelegate: NSObject, NSApplicationDelegate { | |
| @IBOutlet var window: NSWindow | |
| @IBOutlet var label: NSTextField | |
| func applicationDidFinishLaunching(aNotification: NSNotification?) { | |
| // Insert code here to initialize your application | |
| } |
