![\"Swift](\"https:\/\/img.shields.io\/badge\/Swift-3.0-orange.svg?style=flat\")
<\/p>\n<\/p>\n
Hey! Interested in an Swift 3.0 is introducing a number of changes, the least of which is moving to conformance of the ratified API naming conventions<\/a>. If you read through the naming conventions you’ll see that the overarching theme is one of streamlining and simplification.<\/p>\n Let’s take a look at a few examples of this streamlining with this 2.2 script Swift 3.0 changes the The And finally<\/i>, Let’s take a look at another change in Swift 3.0 (which I appreciate), and that’s the named parameter<\/i> is now required for the first argument to a function. For example, in Swift 2.2 the function A few more examples of changes made:<\/p>\n Regardless of what you think about the wisdom of this The Swift 3.0 complains that Our next error is The placement of the That resulted in As a part of the Great Renaming<\/i> the In addition to renaming classes, there has been a significant number of API changes centered around simplifying<\/i> things. A great example of this simplification can be found in formatting dates and creating dates from strings. See our post on handling dates<\/a> for more examples.<\/p>\n Using Is that all there is to Swift 3.0 you ask? Of course not! The Swift Evolution<\/a> repository has a complete list of all of the various changes. Have a look!<\/p>\n There are a number of ways to start playing with Swift 3.0 today. Apple releases snapshot builds every so often on the official Download Swift<\/a> page. Make sure and grab one of the Trunk Development (master)<\/a> snapshots. The snapshots are in the form of If you’re running Ubuntu 14.04 or Ubuntu 15.10 and like the convenience of installing software with apt-get<\/code> repository for Swift 3.0? We’ve got packages for Xenial, Wily, and Trusty<\/a>.<\/p>\nswiftcat.swift<\/code>:<\/p>\n\nimport Glibc\n\nguard Process.arguments.count == 2 else {\n print(\"Usage: swiftcat FILENAME\")\n exit(-1)\n}\n\nlet filename = Process.arguments[1]\n\nlet BUFSIZE = 1024\nvar pp = popen(\"cat \" + filename, \"r\")\nvar buf = [CChar](count:BUFSIZE, repeatedValue:CChar(0))\n\nwhile fgets(&buf, Int32(BUFSIZE), pp) != nil {\n print(String.fromCString(buf)!, terminator:\"\")\n}\n\nexit(0)\n<\/pre>\n(count:repeatedValue)<\/code> function signature for array initialization to (repeating:count:)<\/code>. So rather than var buf = [CChar](count:BUFSIZE, repeatedValue:CChar(0))<\/code> we will use var buf = [CChar](repeating:0, count:BUFSIZE)<\/code> (note that we also simplified CChar(0)<\/code> to just 0<\/code>).<\/p>\nfromCString<\/code> String<\/code> method has been removed in favor of an initializer in the form of init(cString:)<\/code>. As an initializer it also guarantees an object will be returned, so there’s no need for using the !<\/code>: print (String(cString:buf), terminator:\"\")<\/code><\/p>\nCommandLine<\/code> is used instead of Process<\/code>. Our new Swift 3.0 version of swiftcat.swift<\/code>:<\/p>\n\nimport Glibc\n\nguard CommandLine.arguments.count == 2 else {\n print(\"Usage: swiftcat FILENAME\")\n exit(-1)\n}\n\nlet filename = CommandLine.arguments[1]\n\nlet BUFSIZE = 1024\nvar pp = popen(\"cat \" + filename, \"r\")\nvar buf = [CChar](repeating:0, count:BUFSIZE)\n\nwhile fgets(&buf, Int32(BUFSIZE), pp) != nil {\n print(String(cString:buf), terminator:\"\")\n}\n\nexit(0)\n<\/pre>\nfunc translate(text:String, from:String, to:String)<\/code> would be invoked with something like translate(\"Hello world\", from:\"en\", to:\"es\")<\/code>. In Swift 3.0 the text<\/code> parameter label is required: translate(text:\"Hello world\", from:\"en\", to:\"es\")<\/code>.<\/p>\nString<\/code> extension, this is functional Swift 2.2 code:<\/p>\n\nextension String {\n subscript (r: Rangevalue of type 'Index' (aka 'String.CharacterView.Index') has no member 'advancedBy'<\/code>. That’s because the function has changed from advancedBy(_:Index)<\/code> to advanced(by:Index)<\/code> (and somewhere buried in the API guidelines is a rationale as to the change).<\/p>\ninit(start:end:) is unavailable: use the '..<' operator<\/code>. I must admit that the ..<<\/code> operator looks weird<\/i> (there, I said it), but okay, we’ll play along and update the code to return self[Range(startIndex..<endIndex)]<\/code>.<\/p>\nIn-N-Out (Burger)<\/h3>\n
inout<\/code> keyword has also changed. In Swift 2.2 our function for emulating certain ncurses<\/code> calls looked like this:<\/p>\n\nfunc getmaxyx(window:UnsafeMutablePointer
error: 'inout' before a parameter name is not allowed, place it before the parameter type instead<\/code>, so now we do this:<\/p>\n\nfunc getmaxyx(window:UnsafeMutablePointer
Great Renaming<\/h3>\n
NS<\/code> prefix has been dropped from much of the Foundation classes. NSThread<\/code> is now Thread<\/code>, NSDate<\/code> is now Date<\/code>. You get the idea.<\/p>\nNotifications<\/h3>\n
NSNotificationCenter<\/code> has also changed between Swift 2.x and Swift 3.0. As a part of the Great Renaming the notification center is now simply named NotificationCenter<\/code>. For a complete writeup on notifications see our Notifications and userinfo with Swift 3.0<\/a> post.<\/p>\nBut Wait!<\/h3>\n
Get Started With Swift 3.0<\/h2>\n
.tar.gz<\/code> files that can be extracted on your filesystem.<\/p>\napt-get<\/code>, you can also try out our Swift 3.0 Ubuntu Packages<\/a>.<\/p>\n