Sequence and IteratorProtocol


Welcome to Lesson 5 of Advanced Swift. When it comes to learning new features, I've been using the microwave analogy that things just work because smart engineers have designed them. But, there are times you might have to create your own custom microwave. For example, you might want to create one for yourself during the winter because it's hard to code with frozen fingers. Then, you've got know all. In this lesson, let's find out the secret behind the Swift for-in loop and learn how to create our own custom types that have the magic.


What goes under the hood of a for-in loop.

Take For Granted

When you first learned Swift or other programming languages, you've probably used the feature below without giving a second thought. (I didn't)

let iOSSkills = ["Swift", "UIKIt", "RxSwift", "TDD"]
for skill in iOSSkills {
// Prints "Swift"
// Prints "UIKIt"
// Prints "RxSwift"
// Prints ""TDD""

Let us convert a String value into CharacterView and loop each character.

for character in ("Bob the Developer").characters {
// "B"
// "o"
// "b"
// ...
// "r"

Important: The Swift for-in loop exists since Array<String> and CharacterView both conforms to Sequence and IteratorProtocol.

Behind the Scene

First, the iOSSkill, whose type is Array<String> conforms to Sequence, has the required method, makeIterator. The method returns an object that conforms to IteratorProtocol. The returned object has a required method called, next() which returns the next element with an optional type.

var skillIterator = iOSSkills.makeIterator()

while let skill = {

// Prints "Swift"
// Prints "UIKIt"
// Prints "RxSwift"
// Prints ""TDD""

It also applies to Array<Int>.

let numbers = [2, 3, 5, 7]
var numbersIterator = numbers.makeIterator() // Optional(5)

Custom Type

Sequence Protocol

Let us create our own struct that conforms to Sequence. The struct is called, MyCountdown. The struct has the required method, makeIterator. The method returns an object that conforms to ProtocolIterator.

struct MyCountdown: Sequence {
  let start: Int

  func makeIterator() -> CountdownIterator {
    return CountdownIterator(self)


Let us create a struct, CountdownIterator that conforms to IteratorProtocol. The struct contains the required method, next() which returns an element.

struct CountdownIterator: IteratorProtocol {
  let countdown: MyCountdown
  var times = 0

  init(_ countdown: MyCountdown) {
    self.countdown = countdown

  mutating func next() -> Int? {
    let nextNumber = countdown.start - times
    guard nextNumber > 0
      else { return nil }

    times += 1
    return nextNumber


Let us find out if the makeIterator and next methods work.

var threeTwoOne = MyCountdown(start: 3)
var iterator = threeTwoOne.makeIterator() // 3 // 2 // 1


The MyCountdown. is eligible for the Swift for-in loop.

for count in threeTwoOne {

Source Code



Swift Standard Library Functions

Swift Change Log


API Reference - IteratorProtocol

Ray Wenderlich - Building Custom Collection Swift

Protocols in Swift by Chris Eidhof

How To Conform to the Sequence Protocol - Natasha The Robot


First, you've learned the hidden implementation by the Swift for-in loop. To make types eligible for the magic, it has to conform to the Sequence protocol and has the required method that returns an object that conforms to IteratorProtocol. The iterator object also has the required method of next() to get the next element. The word sequence sounds as if types must look like a dictionary, array, or set. It doesn't have to. Again, the purpose of this lesson was not introduce you to various protocols. It was to let you know how native types conform to pre-written protocols and has added features like a for-in loop. If you wish to study, I recommend you to take a look at the references and read the documentation.

In the following lesson, you will learn how to execute swift files using Terminal and how Xcode sends error messages, a.k.a, the red marks.

Note: Learn Swift with Bob is available on Udemy. If you wish to receive a discount link, you may sign up here.

results matching ""

    No results matching ""