Convenience initializers in Swift - Time & Space Complexity

Time Complexity: Convenience initializers

O(n)

Understanding Time Complexity

When using convenience initializers in Swift, it's helpful to know how the time to create an object changes as input grows.

We want to see how the number of steps to initialize an object scales with input size.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

class NumberList {
    var numbers: [Int]

    init(numbers: [Int]) {
        self.numbers = numbers
    }

    convenience init(count: Int) {
        var temp = [Int]()
        for i in 1...count {
            temp.append(i)
        }
        self.init(numbers: temp)
    }
}
    

This code creates a list of numbers either from an existing array or by building one from 1 to count.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop that appends numbers from 1 to count.
• How many times: Exactly count times, once for each number.

How Execution Grows With Input

As the count grows, the loop runs more times, adding one number each time.

Input Size (count)	Approx. Operations
10	10 appends
100	100 appends
1000	1000 appends

Pattern observation: The work grows directly with the input size; doubling count doubles the steps.

Final Time Complexity

Time Complexity: O(n)

This means the time to initialize grows linearly with the number of items you want to create.

Common Mistake

[X] Wrong: "Convenience initializers always run instantly regardless of input size."

[OK] Correct: Because if the initializer builds or processes data in a loop, the time depends on how much data it handles.

Interview Connect

Understanding how initializers scale helps you write efficient code and explain your design choices clearly in interviews.

Self-Check

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

Practice

1. What is the main purpose of a convenience initializer in Swift?

easy

A. To provide an easier way to create an object by calling a designated initializer

B. To override a superclass initializer

C. To create a completely new object without calling any other initializer

D. To deallocate an object before it is destroyed

Solution

1. Step 1: Understand the role of convenience initializers

   Convenience initializers are shortcuts to create objects more easily by calling a designated initializer.

2. Step 2: Compare options with this role

   Only To provide an easier way to create an object by calling a designated initializer describes this purpose correctly; others describe unrelated concepts.

3. Final Answer:

   To provide an easier way to create an object by calling a designated initializer -> Option A

4. Quick Check:

   Convenience initializer = shortcut calling designated initializer [OK]

Hint: Convenience initializers always call a designated initializer [OK]

Common Mistakes:

• Thinking convenience initializers create objects independently
• Confusing convenience initializers with deinitializers
• Believing convenience initializers override superclass initializers

2. Which of the following is the correct syntax for a convenience initializer in Swift?

easy

A. convenience func init(name: String) { self.init() }

B. init convenience(name: String) { self.init() }

C. func convenience init(name: String) { self.init() }

D. convenience init(name: String) { self.init() }

Solution

1. Step 1: Recall the correct syntax for convenience initializers

   In Swift, the keyword convenience comes before init without any function keyword.

2. Step 2: Check each option

   convenience init(name: String) { self.init() } matches the correct syntax. Options B, C, and D misuse keywords or order.

3. Final Answer:

   convenience init(name: String) { self.init() } -> Option D

4. Quick Check:

   Keyword order: convenience before init [OK]

Hint: Remember: 'convenience' keyword comes before 'init' [OK]

Common Mistakes:

• Placing 'convenience' after 'init'
• Using 'func' keyword with initializers
• Incorrect keyword order causing syntax errors

3. Consider the following Swift code:

class Car {
    var color: String
    init(color: String) {
        self.color = color
    }
    convenience init() {
        self.init(color: "Red")
    }
}
let myCar = Car()

What is the value of myCar.color?

medium

A. nil

B. "Red"

C. "" (empty string)

D. Compilation error

Solution

1. Step 1: Understand the initializers in the Car class

   The designated initializer sets the color property. The convenience initializer calls the designated one with "Red".

2. Step 2: Analyze the object creation

   Creating myCar with Car() calls the convenience initializer, which sets color to "Red".

3. Final Answer:

   "Red" -> Option B

4. Quick Check:

   Convenience init sets color to "Red" [OK]

Hint: Convenience init calls designated init with default values [OK]

Common Mistakes:

• Assuming color is empty or nil without initialization
• Thinking convenience init does not call designated init
• Expecting compilation error due to missing default init

4. Identify the error in this Swift class using a convenience initializer:

class Person {
    var name: String
    convenience init() {
        self.name = "Unknown"
    }
    init(name: String) {
        self.name = name
    }
}

medium

A. Convenience initializer must call a designated initializer, not assign properties directly

B. Designated initializer must be marked as convenience

C. Property 'name' must be optional

D. No error, code is correct

Solution

1. Step 1: Recall rules for convenience initializers

   A convenience initializer must call another initializer in the same class, not assign properties directly.

2. Step 2: Check the convenience init implementation

   Here, self.name = "Unknown" is assigned directly, which is not allowed.

3. Final Answer:

   Convenience initializer must call a designated initializer, not assign properties directly -> Option A

4. Quick Check:

   Convenience init must call designated init [OK]

Hint: Convenience init cannot set properties directly; must call designated init [OK]

Common Mistakes:

• Assigning properties directly in convenience initializer
• Marking designated initializer as convenience
• Making properties optional unnecessarily

5. You want to create a Swift class Rectangle with a designated initializer that takes width and height, and a convenience initializer that creates a square by taking only one side length. Which of the following implementations correctly uses a convenience initializer?

hard

A. class Rectangle {
var width: Double
var height: Double
init(width: Double, height: Double) {
self.width = width
self.height = height
}
convenience init(side: Double) {
self.width = side
self.height = side
}
}

B. class Rectangle {
var width: Double
var height: Double
convenience init(width: Double, height: Double) {
self.width = width
self.height = height
}
init(side: Double) {
self.width = side
self.height = side
}
}

C. class Rectangle {
var width: Double
var height: Double
init(width: Double, height: Double) {
self.width = width
self.height = height
}
convenience init(side: Double) {
self.init(width: side, height: side)
}
}

D. class Rectangle {
var width: Double
var height: Double
init(width: Double, height: Double) {
self.width = width
self.height = height
}
convenience init(side: Double) {
self.height = side
}
}

Solution

1. Step 1: Identify designated and convenience initializers

   The designated initializer takes width and height. The convenience initializer should call the designated one.

2. Step 2: Check each option for correct usage

   class Rectangle { var width: Double var height: Double init(width: Double, height: Double) { self.width = width self.height = height } convenience init(side: Double) { self.init(width: side, height: side) } } correctly defines the designated init and the convenience init calls it with equal sides. Others either misuse convenience keyword or assign properties directly.

3. Final Answer:

   class Rectangle { var width: Double var height: Double init(width: Double, height: Double) { self.width = width self.height = height } convenience init(side: Double) { self.init(width: side, height: side) } } -> Option C

4. Quick Check:

   Convenience init calls designated init with side values [OK]

Hint: Convenience init must call designated init with all required parameters [OK]

Common Mistakes:

• Marking designated initializer as convenience
• Assigning properties directly in convenience initializer
• Not calling designated initializer from convenience initializer