Protocol conformance in Swift - Time & Space Complexity

Time Complexity: Protocol conformance

O(n)

Understanding Time Complexity

When we use protocols in Swift, we want to know how fast the program runs when it checks if a type follows a protocol.

We ask: How does the time to confirm protocol conformance change as we add more types or protocols?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

protocol Greetable {
    func greet()
}

struct Person: Greetable {
    func greet() {
        print("Hello!")
    }
}

let p = Person()
p.greet()

This code defines a protocol and a struct that follows it, then calls the protocol method.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Calling the method defined by the protocol.
• How many times: Once in this example, but could be many times if called repeatedly.

How Execution Grows With Input

When calling a protocol method, the time depends on how many calls you make, not on how many types conform.

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

Pattern observation: The time grows directly with the number of calls, not with the number of types or protocols.

Final Time Complexity

Time Complexity: O(n)

This means the time grows linearly with how many times you call the protocol method.

Common Mistake

[X] Wrong: "Checking if a type conforms to a protocol takes longer as more types conform."

[OK] Correct: Swift uses fast lookups for protocol conformance, so checking does not slow down with more types.

Interview Connect

Understanding how protocol conformance affects speed helps you write clear and efficient Swift code, a skill valued in many coding challenges.

Self-Check

"What if we used a protocol with associated types? How would that affect the time complexity of calling methods?"

Practice

1. What does it mean for a Swift type to conform to a protocol?

easy

A. It can only be a class, not a struct or enum.

B. It inherits all properties and methods from the protocol automatically.

C. It implements all required methods and properties defined by the protocol.

D. It must override all methods from the protocol.

Solution

1. Step 1: Understand protocol requirements

   A protocol defines methods and properties that a type must implement to conform.

2. Step 2: Check what conformance means

   Conforming means the type provides implementations for all required members.

3. Final Answer:

   It implements all required methods and properties defined by the protocol. -> Option C

4. Quick Check:

   Protocol conformance = Implement required members [OK]

Hint: Conformance means implementing all required protocol parts [OK]

Common Mistakes:

• Thinking conformance means inheritance
• Believing only classes can conform
• Assuming methods must be overridden

2. Which of the following is the correct syntax to declare that a struct conforms to a protocol named Drawable?

easy

A. struct Shape inherits Drawable { }

B. struct Shape : Drawable { }

C. struct Shape implements Drawable { }

D. struct Shape extends Drawable { }

Solution

1. Step 1: Recall Swift syntax for protocol conformance

   Swift uses a colon (:) after the type name to declare protocol conformance.

2. Step 2: Match syntax options

   Only struct Shape : Drawable { } uses the correct colon syntax for protocol conformance.

3. Final Answer:

   struct Shape : Drawable { } -> Option B

4. Quick Check:

   Protocol conformance syntax uses ':' [OK]

Hint: Use ':' after type name to conform to protocol [OK]

Common Mistakes:

• Using 'implements' or 'inherits' keywords
• Confusing inheritance with protocol conformance
• Using 'extends' which is not Swift syntax

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

protocol Greetable {
    func greet() -> String
}

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

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

medium

A. Hello!

B. Error: Missing greet() implementation

C. nil

D. Hello! Person

Solution

1. Step 1: Check protocol and struct conformance

   The protocol requires a greet() method returning String. Person implements greet() returning "Hello!".

2. Step 2: Analyze print output

   Calling p.greet() returns "Hello!", so print outputs that string.

3. Final Answer:

   Hello! -> Option A

4. Quick Check:

   Implemented greet() returns "Hello!" [OK]

Hint: Implemented method returns string printed directly [OK]

Common Mistakes:

• Assuming missing implementation error
• Expecting default protocol method output
• Confusing print output with type description

4. Identify the error in this Swift code that tries to conform to the Equatable protocol:

struct Point: Equatable {
    var x: Int
    var y: Int
}

medium

A. Missing implementation of == operator function

B. Struct cannot conform to Equatable

C. Properties must be constants (let) to conform

D. No error, code compiles fine

Solution

1. Step 1: Understand Equatable conformance rules

   Swift automatically synthesizes == for structs with Equatable properties.

2. Step 2: Check struct properties and conformance

   Both x and y are Int (Equatable), so compiler provides == automatically.

3. Final Answer:

   No error, code compiles fine -> Option D

4. Quick Check:

   Automatic Equatable synthesis = No error [OK]

Hint: Swift auto-synthesizes Equatable for simple structs [OK]

Common Mistakes:

• Thinking manual == is always needed
• Believing structs can't conform
• Assuming properties must be let

5. Given this protocol and struct, how can you modify Vehicle to conform to CustomStringConvertible and print a description?

protocol CustomStringConvertible {
    var description: String { get }
}

struct Vehicle {
    var make: String
    var model: String
}

hard

A. Add extension Vehicle: CustomStringConvertible { var description: String { "\(make) \(model)" } }

B. Add func description() -> String { return "\(make) \(model)" } inside Vehicle

C. Add var description: String = "\(make) \(model)" inside Vehicle

D. Add override var description: String { "\(make) \(model)" } inside Vehicle

Solution

1. Step 1: Understand protocol property requirement

   CustomStringConvertible requires a read-only computed property 'description' of type String.

2. Step 2: Implement description correctly

   Implementing description as a computed property in an extension is the correct way.

3. Final Answer:

   Add extension Vehicle: CustomStringConvertible { var description: String { "\(make) \(model)" } } -> Option A

4. Quick Check:

   Computed property in extension = Correct conformance [OK]

Hint: Use computed property in extension for protocol conformance [OK]

Common Mistakes:

• Trying to add description as a method
• Using stored property instead of computed
• Using override keyword in struct