This is for Swift Version 2.2 & earlier. I will be adding the snippet of code for the changes the Swift 3.x have introduced.
What are the Collection Type & Sequence Type Protocols?
The Collection Type, Sequence Type & Generator Type Protocols define rules that govern how different data structures or collections of data can be used, interacted with and operated within the Swift programming language. The CollectionType is a special case of the SequenceType.
Why do we need such Protocols?
Lets take the example of the Swift For-Loop.
var arrOfStrings : [String] = [String]() arrOfStrings.append("Jill") arrOfStrings.append("Jack") arrOfStrings.append("John") arrOfStrings.append("Jane") for name in arrOfString { print("The name is \(name)") }
Now, if we have created our own data type. We would not be able to use the above for-loop as it would not conform to the … type protocols. The for-loop is expecting a data structure that acts and behaves in a way that is governed by the … protocols.
Just like the for-loop example above there are many other features within the Swift Programming Language that expect data structures to act and behave in a particular way. By designing our data structures to conform to these protocols we can make the easily compatible with the existing code and language features out there.
How do we use these protocols for our own data structures?
First we need to decide what kind of collection are we making. For the sake of this example I will create a Custom Stack.
class CustomStack<Element> { var data : [Element] = [Element]() func push(Element newElement : Element) { data.append(newElement) } func pop() -> Element { return data.removeLast() } }
The above code is very simple for the purpose of this exercise. Its a stack. Which is internally really an Array. It has functions to push data and pop data. We are now going to convert this type to a collection to conform to the CollectionType protocol.
Implementing the Indexable Protocol methods
As a first step we are going to make our CustomStack conform to the Indexable Protocol.
extension CustomStack : Indexable { //INDEXABLE PROTOCOLS typealias Index = Int var startIndex : Int { return 0 } var endIndex: Int { return (data.count - 1) } subscript (position : Int) -> Element { return data[position] } }
The above change makes the data structure conform to the Indexable protocol. This is a requirement for it to be of type CollectionType. In order to conform to the Indexable protocol we need to implement a few computed properties. Let us look at the changes
typealias Index = Int
This line informs the system that the Indexing type for my data structure is an Int.
var startIndex : Int { return 0 } var endIndex: Int { return (data.count - 1) }
The next 2 are computed properties. Each provides the implementation of the startIndex and endIndex properties. Note that the type for both is Int as we have declared the Index type earlier as Int.
subscript (position : Int) -> Element { return data[position] }
The last implementation is of subscript. This provides the implementation to access an Element from the Stack using the Subscript operator.
Implementing the Sequence Type Protocol
Next we will implement the Sequence Type Protocol methods.
extension CustomStack : SequenceType { typealias Generator = AnyGenerator<Element> func generate() -> Generator { var index = 0 return AnyGenerator(body: {() -> Element? in if index < self.data.count { let res = self.data[index] index += 1 return res } return nil }) } }
Let us examine this code line by line.
typealias Generator = AnyGenerator<Element>
Objects of type Generator allow us to navigate through our collection. Quite like how iterators work in C++. This line specifies the type to be AnyGenerator for Elements.
func generate() -> Generator
Next we start the implementation of the generate function. This is required as part of the SequenceType protocol.
var index = 0
This index variable is used to track the element that is currently being accessed.
return AnyGenerator(body: {() -> Element? in if index < self.data.count { let res = self.data[index] index += 1 return res } return nil })
The return statement is the main statement. Here we are creating an object of type AnyGenerator. As an argument to the constructor call we are passing in a closure that will be used to iterate through the sequence. Note that the closure captures the index variable and holds a reference to its value even though we have left the original function.
Implementing the Collection Type Protocol
Next we will implement the Collection Type Protocol methods. We don’t really need to implement a lot in order to conform to the CollectionType protocol. In fact, if we just conform to the CollectionType protocol and use the implementations of the previous 2 extensions we should be just fine. However, for the sake of demonstration we are implementing the subscript functionality within the CollectionType.
extension CustomStack : CollectionType { typealias SubSequence = CustomStack<Element> subscript (bounds: Range<CustomStack.Index>) -> CustomStack.SubSequence { let newStack : CustomStack<Element> = CustomStack<Element>() for i in bounds.startIndex...bounds.endIndex { newStack.push(Element: data[i]) } return newStack } }
Let us look at the code line by line.
typealias SubSequence = CustomStack<Element>
Again, as before this line indicates that the SubSequence type is actually a CustomStack.
subscript (bounds: Range<CustomStack.Index>) -> CustomStack.SubSequence
Here we start the implementation of the subscript functionality.
let newStack : CustomStack<Element> = CustomStack<Element>() for i in bounds.startIndex...bounds.endIndex { newStack.push(Element: data[i]) } return newStack
The rest of the code is the implementation of the subscript range behaviour. One can have different implementations to achieve the same result.
CollectionType Video
Conclusion
As we can see, by designing our data structure to conform to a particular set of protocols. We have made it possible for our data structure to take advantages of the different features, functionalities and even API’s available within the Swift Language and the Frameworks used as a part of iOS, macOS, watchOS & tvOS development.
Pingback: COLLECTION TYPE, SEQUENCE TYPE & INDEXABLE TYPE – Update | Arun Patwardhan's Blog