Type aliases for readability in Swift - Time & Space Complexity

Time Complexity: Type aliases for readability

O(1)

Understanding Time Complexity

Let's explore how using type aliases affects the time it takes for a program to run.

We want to see if giving new names to types changes how fast the code works.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

    typealias Point = (x: Int, y: Int)

    func distance(from p1: Point, to p2: Point) -> Double {
        let dx = p2.x - p1.x
        let dy = p2.y - p1.y
        return (Double(dx * dx + dy * dy)).squareRoot()
    }
    

This code defines a type alias for a point and calculates the distance between two points.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Simple arithmetic and a square root calculation.
• How many times: Each operation runs once per function call.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations
10	6 calculations
100	6 calculations
1000	6 calculations

Pattern observation: The number of operations remains constant regardless of input size.

Final Time Complexity

Time Complexity: O(1)

This means the time to run the function stays the same no matter the input size.

Common Mistake

[X] Wrong: "Using type aliases makes the code slower because it adds extra steps."

[OK] Correct: Type aliases only rename types for clarity and do not add any extra work when the program runs.

Interview Connect

Understanding that type aliases improve code readability without affecting speed shows you know how to write clean and efficient code.

Self-Check

"What if the function used an array of points instead of just two? How would the time complexity change?"