はてなブックマーク

Chris Lattner writes on Looking back on Swift 3 and ahead to Swift 4.  Key tl;dr points: Open source is great but you can’t make everyone happy. Swift 3 in Fall 2016. Swift 3.x will release in Spring 2017. Swift 4 in Fall 2017, not counting minor releases for bugs/compatibility (e.g. 3.0.1) Swift 4 must deliver its source stability promise, plus resilience, ABI, improving generics, strings, etc. S

Trying to write cross-platform code for drawing routines is ridiculously frustrating. It’s never just a matter of creating cross-platform type aliases. UIColor and NSColor are cousins, not brothers. UIBezierPath and NSBezierPath are slightly more distantly related, especially when it comes to adding curves and retrieving an underlying cgPath. Although a lot of tech debuts on Cocoa, it often gets r

The Swift 4 release process targets Fall 2017: Swift 4 is a major release that is intended to be completed in the fall of 2017. It pivots around providing source stability for Swift 3 code while implementing essential feature work needed to achieve binary stability in the language. It will contain significant enhancements to the core language and Standard Library, especially in the generics system

Last night, someone was asking what you call the things created by types. My take on the subject is this: Classes, structures, and enumerations are constructs. You create new instances by calling a constructor, even when building things that aren’t reference types. I avoid calling reference types “objects”. I stick with instances, following the Swift Programming Language’s lead, e.g. “Use the init

Nichole Jacque writes on the swift-dev email list: Hello everyone. We have cut the swift-3.0-preview-1-branch. Any changes to that branch need to go through pull requests, and be approved by the release manager. For more details on the Swift 3.0 Release Process, please check out the blog post: https://swift.org/blog/swift-3-0-release-process/ Marc points out in the comments that “The first develop

Code completion provides better matches with fewer keystrokes and makes it easier to find what you’re looking for. You can type just the uppercase letters of a method name. Typing “myDelegate.tveh”, where myDelegate is a UITableViewDelegate, gives tableView(_ tableView: UITableView, estimatedHeightForRowAtIndexPath indexPath: NSIndexPath) -> CGFloat as the first completion. You’ll also get complet

Traditional Cocoa has a bad dictionary habit. From user info to font options to AV settings, NSDictionary has long acted as the Cocoa workhorse for passing data. Dictionaries are flexible, easy to use, and a minefield of potential disasters. In this post, I’m going to discuss an alternative approach, one that’s far more Swift-y. It’s not yet a completely turn-key solution but I think its one that

Got a really good question today: How does Swift 2.0’s new error handling mechanisms work with asynchronous execution. I don’t have an authoritative answer but I do have a some thoughts to share. Asynchrony and Throw Many asynchronous Cocoa calls use completion blocks.  You place a request and the completion block executes when the request completes, regardless of whether that request succeeded or

The topic of command-line Swift popped up on the swift-language mail list today, and it occurred to me that it might be helpful to share my little starter skeleton. The following pulls in the base app name (for usage() or whatever), and polls the dashed arguments and their associated values. (Update: see below about scripting, via Practical Swift.) import Foundation let arguments = NSProcessInfo.p

Been chatting about 1.0 — when it’s coming, what it will involve. The only thing that seems likely is that 1.0 will compile for 8.0, not that 1.0 will be code stable or act as a language development endpoint. Chris Lattner wrote, “Our goal for Swift 1.0 is for *apps* to be binary compatible with the OS, not for Swift 1.0 frameworks to be compatible with swift 2.0 frameworks.  The formal goal (what

Many exciting updates in Beta 4. A few thoughts. Jumpbar support for //MARK:. Finally, Swift has a #pragma mark equivalent Minimum deployment enforcement. If you’ve been having fun deploying to iOS 6, the party is over. Strides. Ranges now use stride() instead of by(). I’m still waiting for Xcode to finish downloading so I can test this, but the idea is that you use stride(from, to/through, by) in

Right now in Xcode 6, there are plenty of simulators to choose from but did you know that you could create your own simulators and customize them for specific testing needs? The simctl command line utility, which you find at /Applications/Xcode6-Beta.app/Contents/Developer/usr/bin/simctl, enables you to create new custom simulators built to your specifications. You start by creating a device, sett

A while back, I wrote about how handy it was to redirect a man page into Preview. This allows you to keep the man page open, search it, and generally have a better user experience than struggling with more (or less) to navigate through the information provided there. man -t apropos | open -fa Preview Recently, someone asked me about more modern command line interaction, specifically, commands that