{"id":291,"date":"2014-06-28T07:01:27","date_gmt":"2014-06-28T13:01:27","guid":{"rendered":"http:\/\/dev.iachieved.it\/iachievedit\/?p=291"},"modified":"2014-06-28T07:01:27","modified_gmt":"2014-06-28T13:01:27","slug":"an-adventure-in-arrays-with-apple-swift","status":"publish","type":"post","link":"https:\/\/dev.iachieved.it\/iachievedit\/an-adventure-in-arrays-with-apple-swift\/","title":{"rendered":"An Adventure in Arrays with Apple Swift"},"content":{"rendered":"

No, this is not another blog post restating the obvious or reiterating what you could have read in Apple’s Swift language reference<\/a>. Our goal here is to show you how to regain the lost mojo of the lastObject<\/code> method of NSArray<\/code>.<\/p>\n

For the most part arrays in Swift are mundane and appear syntactically similar to array instantiation and usage in many other languages. A bit of Python:<\/p>\n

[python]
\nshoppingList = [‘bananas’, ‘milk’, ‘vanilla ice cream’]
\nitemCount = len(shoppingList)
\nprint "There are %d items." % itemCount
\nfor item in shoppingList:
\n print "I need to buy %s." % item
\nprint "The most important item on my list is definitely %s." % shoppingList[-1]
\n[\/python]<\/p>\n

How about some Ruby:<\/p>\n

[ruby]
\nshoppingList = [‘bananas’, ‘milk’, ‘vanilla ice cream’]
\nitemCount = shoppingList.count
\nputs "There are #{itemCount} items."
\nshoppingList.each do |item|
\n puts "I need to buy #{item}"
\nend
\nputs "The most important item on my list is definitely #{shoppingList[-1]}."
\n[\/ruby]<\/p>\n

In Objective-C we would use an NSArray<\/code> of NSString<\/code> objects, and the most important item on our list could be retrieved with lastObject<\/code>:<\/p>\n

[objc]
\nNSArray* shoppingList = @[@"bananas", @"milk", @"vanilla ice cream"];
\nNSLog(@"The most important thing on my list is definitely %@.", [shoppingList lastObject]);
\n[\/objc]<\/p>\n

Let’s try that in Swift with:<\/p>\n

[objc]
\nvar shoppingList = ["bananas", "milk", "vanilla ice cream"]
\nvar itemCount = shoppingList.count
\nprintln("There are \\(itemCount) items.")
\nfor item in shoppingList {
\n println("I need to buy \\(item).")
\n}
\nprintln("The most important item on my list is definitely \\(shoppingList.lastObject)")
\n[\/objc]<\/p>\n

Before we get to the fact that lastObject<\/code> doesn’t work, notice again how scripty<\/i> Swift feels. We suppose there are only so many syntactical constructs for creating arrays <\/a>. We’re glad Swift doesn’t borrow too much<\/i> from Erlang.<\/p>\n

But we digress. We assume Swift, like Objective-C, will give us a lastObject<\/code> property or method on our array. Oh, no, it doesn’t. Playground execution failed: error: :18:61: error: 'Array' does not have a member named 'lastObject'
\nprintln(\"The most important item on my list is definitely \\(shoppingList.lastObject)\")<\/code>. Let’s try the array[-1]<\/code> notation that’s popular in Python and Ruby (and I’m sure others) for obtaining the last item in an array:<\/p>\n

[objc]
\nprintln("The most important item on my list is definitely \\(shoppingList[-1])")
\n[\/objc]<\/p>\n

The horror! fatal error: Negative Array index is out of range
\nPlayground execution failed: error: Execution was interrupted, reason: EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0).<\/code> Of course we know<\/i> that Swift arrays are index-based, and that the first index is 0, and the last index of the array is count - 1<\/code>. So perhaps we can do that:<\/p>\n

[objc]
\nprintln("The most important item on my list is definitely \\(shoppingList[shoppingList.count-1]).")
\n[\/objc]<\/p>\n

We can<\/i> do that, but how awful looking. Yuck, yuck, yuck. If it feels<\/i> wrong chances are good that it is, and that just doesn’t look right. Oddly enough, Apple does provide a removeLast<\/code> method on the array, but it does indeed remove<\/i> the last element (sort of like a stack pop<\/code> function):<\/p>\n

[objc]
\nvar lastItem = shoppingList.removeLast()
\nprintln("The most important item on my list is definitely \\(lastItem), and now there are \\(shoppingList.count) items left.")
\n[\/objc]<\/p>\n

results in “The most important item on my list is definitely vanilla ice cream, and now there are 2 items left.”<\/p>\n

So, what if we truly do want to access<\/i> but not remove<\/i> the last item on the list? Here’s a nice gem we found on StackOverflow<\/a> that provides this functionality by extending<\/b> the Array<\/code> type. Extensions are the Swift equivalent of Objective-C categories<\/i> that are useful for “adding on” new functionality to an existing class. Here’s the codez (we took a the self.endIndex<\/code> and replaced with simply endIndex<\/code> at the suggestion of another reader):<\/p>\n

[objc]
\nextension Array {
\n var lastObject: T {
\n return self[endIndex – 1]
\n }
\n}
\n[\/objc]<\/p>\n

Let’s try it in the playground:<\/p>\n

[objc]
\nprintln("The most important item on my list is definitely \\(shoppingList.lastObject).")
\n[\/objc]<\/p>\n

now results in what we expect, and that’s the most important item on my list is definitely vanilla ice cream. What can we say, we love banana milk shakes.<\/p>\n","protected":false},"excerpt":{"rendered":"

No, this is not another blog post restating the obvious or reiterating what you could have read in Apple’s Swift language reference. Our goal here is to show you how to regain the lost mojo of the lastObject method of NSArray. For the most part arrays in Swift are mundane and appear syntactically similar to […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-291","post","type-post","status-publish","format-standard","hentry","category-swift"],"_links":{"self":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/291"}],"collection":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/comments?post=291"}],"version-history":[{"count":6,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/291\/revisions"}],"predecessor-version":[{"id":297,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/291\/revisions\/297"}],"wp:attachment":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/media?parent=291"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/categories?post=291"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/tags?post=291"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}