Why protocol-oriented programming matters in Swift - Performance Analysis

Time Complexity: Why protocol-oriented programming matters

O(n)

Understanding Time Complexity

When using protocol-oriented programming, it is important to understand how the program's speed changes as it uses more data or more complex types.

We want to know how the use of protocols affects the time it takes for code to run as input grows.

Scenario Under Consideration

Analyze the time complexity of the following Swift code using protocols.

protocol Drawable {
    func draw()
}

struct Circle: Drawable {
    func draw() {
        print("Drawing Circle")
    }
}

func drawAll(shapes: [Drawable]) {
    for shape in shapes {
        shape.draw()
    }
}

This code defines a protocol and a struct that follows it, then draws all shapes in a list by calling their draw method.

Identify Repeating Operations

Look for loops or repeated calls that affect performance.

• Primary operation: Looping through the array of shapes and calling draw() on each.
• How many times: Once for each shape in the input array.

How Execution Grows With Input

As the number of shapes increases, the number of draw calls grows directly with it.

Input Size (n)	Approx. Operations
10	10 draw calls
100	100 draw calls
1000	1000 draw calls

Pattern observation: The work grows evenly as the input grows; doubling shapes doubles work.

Final Time Complexity

Time Complexity: O(n)

This means the time to draw all shapes grows in a straight line with the number of shapes.

Common Mistake

[X] Wrong: "Using protocols makes the code slower because of extra overhead in method calls."

[OK] Correct: Protocol calls are optimized by Swift, and the main time cost comes from how many times you call methods, not from using protocols themselves.

Interview Connect

Understanding how protocol-oriented code scales helps you write clean, reusable code without worrying about hidden slowdowns as your app grows.

Self-Check

"What if the drawAll function used recursion instead of a loop? How would the time complexity change?"

Practice

1. What is the main purpose of protocols in Swift's protocol-oriented programming?

easy

A. To define a blueprint of methods and properties that a type must implement

B. To store data like variables and constants

C. To create user interfaces

D. To manage memory automatically

Solution

1. Step 1: Understand what protocols represent

   Protocols specify a set of methods and properties that a type must have, acting as a blueprint.

2. Step 2: Differentiate protocols from data storage

   Protocols do not store data themselves; they only define behavior and requirements.

3. Final Answer:

   To define a blueprint of methods and properties that a type must implement -> Option A

4. Quick Check:

   Protocols = Blueprint of behavior [OK]

Hint: Protocols define required behavior, not data storage [OK]

Common Mistakes:

• Thinking protocols store data
• Confusing protocols with classes or structs
• Assuming protocols manage memory

2. Which of the following is the correct syntax to declare a protocol named Drivable in Swift?

easy

A. struct Drivable { func drive() }

B. class Drivable { func drive() }

C. func protocol Drivable() { drive() }

D. protocol Drivable { func drive() }

Solution

1. Step 1: Recall protocol declaration syntax

   Protocols are declared using the keyword protocol followed by the name and curly braces.

2. Step 2: Identify correct method declaration inside protocol

   Inside protocols, methods are declared without implementation, just the signature.

3. Final Answer:

   protocol Drivable { func drive() } -> Option D

4. Quick Check:

   Use 'protocol' keyword and method signature [OK]

Hint: Protocols start with 'protocol' keyword, not class or struct [OK]

Common Mistakes:

• Using class or struct instead of protocol
• Trying to implement method inside protocol
• Incorrect keyword order

3. What will be the output of the following Swift code?

protocol Greetable {
    func greet() -> String
}

struct Person: Greetable {
    func greet() -> String {
        "Hello!"
    }
}

let p = Person()
print(p.greet())

medium

A. Error: Missing method implementation

B. greet()

C. Hello!

D. nil

Solution

1. Step 1: Check protocol and struct conformance

   The struct Person conforms to Greetable and implements greet() returning "Hello!".

2. Step 2: Understand the print statement output

   Calling p.greet() returns "Hello!", which is printed.

3. Final Answer:

   Hello! -> Option C

4. Quick Check:

   Protocol method implemented returns "Hello!" [OK]

Hint: Check if method returns a string and is called correctly [OK]

Common Mistakes:

• Assuming protocol methods print automatically
• Thinking missing implementation error occurs
• Confusing method name with output

4. Identify the error in this Swift code using protocol-oriented programming:

protocol Runnable {
    func run()
}

struct Athlete: Runnable {
    // Missing run() implementation
}

let athlete = Athlete()
athlete.run()

medium

A. Athlete struct must implement run() method

B. Protocol Runnable cannot be used with structs

C. run() method should return a value

D. Cannot create instance of Athlete

Solution

1. Step 1: Check protocol requirements

   The protocol Runnable requires a run() method to be implemented.

2. Step 2: Verify struct conformance

   The struct Athlete does not implement run(), so it does not conform properly.

3. Final Answer:

   Athlete struct must implement run() method -> Option A

4. Quick Check:

   Protocol methods must be implemented in conforming types [OK]

Hint: Check if all protocol methods are implemented in struct/class [OK]

Common Mistakes:

• Assuming protocols can't be used with structs
• Thinking run() must return a value
• Believing instance creation is the error

5. You want to create a reusable logging system in Swift using protocol-oriented programming. Which approach best supports easy reuse and maintenance?

hard

A. Use global variables to store logs

B. Define a protocol Loggable with a log() method, then extend it with default implementation

C. Write separate logging functions in each class without protocols

D. Create a base class Logger and inherit from it everywhere

Solution

1. Step 1: Understand protocol-oriented programming benefits

   Protocols with default implementations allow behavior sharing without inheritance.

2. Step 2: Evaluate options for reuse and maintenance

   Extending a protocol with default log() method lets many types reuse logging easily and maintain code in one place.

3. Final Answer:

   Define a protocol Loggable with a log() method, then extend it with default implementation -> Option B

4. Quick Check:

   Protocols + extensions = reusable, maintainable code [OK]

Hint: Use protocol with default methods for reusable behavior [OK]

Common Mistakes:

• Relying on inheritance instead of protocols
• Duplicating code in each class
• Using global variables for behavior