Adding initializers via extension in Swift - Time & Space Complexity

Time Complexity: Adding initializers via extension

O(n)

Understanding Time Complexity

When we add initializers using extensions in Swift, it is important to understand how this affects the time it takes to create objects.

We want to know how the time to initialize grows as we create more instances.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

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

extension Point {
    init(value: Int) {
        self.x = value
        self.y = value
    }
}

let points = (1...n).map { Point(value: $0) }
    

This code adds a new initializer to the Point struct using an extension, then creates an array of Points using that initializer.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Creating each Point instance using the new initializer.
• How many times: The initializer runs once for each number from 1 to n.

How Execution Grows With Input

Each new Point is created one after another, so the total time grows directly with how many Points we make.

Input Size (n)	Approx. Operations
10	10 initializations
100	100 initializations
1000	1000 initializations

Pattern observation: The time increases evenly as we add more Points.

Final Time Complexity

Time Complexity: O(n)

This means the time to create all Points grows in a straight line with the number of Points.

Common Mistake

[X] Wrong: "Adding an initializer via extension makes object creation slower in a way that grows faster than the number of objects."

[OK] Correct: The initializer code runs once per object, so the total time grows directly with the number of objects, not faster.

Interview Connect

Understanding how adding initializers affects creation time helps you explain how your code scales when making many objects, a useful skill in real projects.

Self-Check

"What if the initializer did some extra work like looping inside it? How would the time complexity change?"

Practice

1. What is the main purpose of adding initializers via extension in Swift?

easy

A. To convert a class into a struct

B. To override existing initializers in the original type

C. To delete initializers from the original type

D. To add new ways to create instances without modifying the original type code

Solution

1. Step 1: Understand what extensions do

   Extensions allow adding new features to existing types without changing their original code.

2. Step 2: Focus on initializers added via extensions

   Adding initializers via extension means creating new ways to make instances without touching the original type's code.

3. Final Answer:

   To add new ways to create instances without modifying the original type code -> Option D

4. Quick Check:

   Extensions add features = A [OK]

Hint: Extensions add, not change original initializers [OK]

Common Mistakes:

• Thinking extensions override existing initializers
• Believing extensions remove initializers
• Confusing extensions with type conversion

2. Which of the following is the correct syntax to add a new initializer to a struct Point via extension?

easy

A. extension Point { init(x: Int, y: Int) { self.x = x; self.y = y } }

B. extension Point { func init(x: Int, y: Int) { self.x = x; self.y = y } }

C. extension Point { init Point(x: Int, y: Int) { self.x = x; self.y = y } }

D. extension Point { initializer(x: Int, y: Int) { self.x = x; self.y = y } }

Solution

1. Step 1: Recall initializer syntax in extensions

   Initializers use the keyword init without a function keyword.

2. Step 2: Check each option's syntax

   extension Point { init(x: Int, y: Int) { self.x = x; self.y = y } } correctly uses init with parameters and assigns properties. Others misuse keywords like func, add extra words, or wrong keywords.

3. Final Answer:

   extension Point { init(x: Int, y: Int) { self.x = x; self.y = y } } -> Option A

4. Quick Check:

   Use init keyword only for initializers [OK]

Hint: Initializers use 'init', not 'func' or 'initializer' [OK]

Common Mistakes:

• Using 'func' instead of 'init' for initializers
• Adding extra words like 'initializer' or type name after 'init'
• Incorrect punctuation or missing braces

3. Given the code below, what will be printed?

struct Rectangle {
    var width: Int
    var height: Int
}

extension Rectangle {
    init(size: Int) {
        self.width = size
        self.height = size
    }
}

let square = Rectangle(size: 5)
print(square.width, square.height)

medium

A. 5 0

B. 0 0

C. 5 5

D. Compilation error

Solution

1. Step 1: Understand the extension initializer

   The extension adds an initializer that sets both width and height to the same size value.

2. Step 2: Analyze the instance creation and print

   Creating square with size: 5 sets width and height to 5. Printing outputs "5 5".

3. Final Answer:

   5 5 -> Option C

4. Quick Check:

   Extension init sets both properties = 5 5 [OK]

Hint: Extension init sets all properties explicitly [OK]

Common Mistakes:

• Assuming default values instead of assigned ones
• Expecting compilation error due to missing original initializer
• Confusing property values after init

4. What is wrong with this extension adding an initializer to a class Car?

class Car {
    var model: String
    init(model: String) {
        self.model = model
    }
}

extension Car {
    init() {
        model = "Unknown"
    }
}

medium

A. Missing call to designated initializer in extension initializer

B. Cannot add initializers to classes via extensions

C. Property model is not declared

D. Extension initializer must have parameters

Solution

1. Step 1: Recall rules for class initializers in extensions

   When adding a convenience initializer in an extension, it must call a designated initializer of the class.

2. Step 2: Check the extension initializer code

   The extension initializer sets model directly but does not call self.init(model:), violating the rule.

3. Final Answer:

   Missing call to designated initializer in extension initializer -> Option A

4. Quick Check:

   Class extension init must call designated init [OK]

Hint: Class extension init must call self.init(...) [OK]

Common Mistakes:

• Forgetting to call designated initializer in class extension
• Thinking extensions can't add initializers to classes
• Assuming properties auto-initialize without init call

5. You want to add an initializer to a struct User via extension that accepts a dictionary [String: String] and sets name and email. Which code correctly implements this, handling missing keys by setting empty strings?

hard

A. extension User {
init(data: [String: String]) {
self.name = data["name"]!
self.email = data["email"]!
}
}

B. extension User {
init(data: [String: String]) {
self.name = data["name"] ?? ""
self.email = data["email"] ?? ""
}
}

C. extension User {
init(data: [String: String]) {
self.name = data["name"]
self.email = data["email"]
}
}

D. extension User {
init(data: [String: String]) {
name = data["name"] ?? ""
email = data["email"] ?? ""
}
}

Solution

1. Step 1: Understand safe unwrapping of dictionary values

   Using ?? "" provides a default empty string if the key is missing, avoiding runtime errors.

2. Step 2: Check property assignment and self usage

   extension User { init(data: [String: String]) { self.name = data["name"] ?? "" self.email = data["email"] ?? "" } } correctly uses self.name and self.email with safe unwrapping. extension User { init(data: [String: String]) { name = data["name"] ?? "" email = data["email"] ?? "" } } misses self. which is required in initializers.

3. Final Answer:

   extension User { init(data: [String: String]) { self.name = data["name"] ?? "" self.email = data["email"] ?? "" } } -> Option B

4. Quick Check:

   Use self and safe default values in init [OK]

Hint: Use 'self.' and '??' for safe dictionary access [OK]

Common Mistakes:

• Force unwrapping dictionary values causing crashes
• Omitting 'self.' when assigning properties in init
• Not providing default values for missing keys