BuildOptional and buildEither in Swift - Time & Space Complexity

Time Complexity: BuildOptional and buildEither

O(n)

Understanding Time Complexity

When using BuildOptional and buildEither in Swift, it's important to understand how the code execution time changes as input grows.

We want to see how these builders affect the number of steps the program takes.

Scenario Under Consideration

Analyze the time complexity of the following Swift code using BuildOptional and buildEither.

func process(values: [Int]?) {
    if let values = values {
        for value in values {
            print(value)
        }
    } else {
        print("No values")
    }
}

func choose(value: Int) {
    switch value {
    case 1: print("One")
    case 2: print("Two")
    default: print("Other")
    }
}
    

This code uses optional handling and conditional branches similar to BuildOptional and buildEither to decide what to run.

Identify Repeating Operations

Look for loops or repeated steps in the code.

• Primary operation: The for-loop that prints each value in the array.
• How many times: Once for each item in the input array if it exists.

How Execution Grows With Input

The number of print operations grows as the number of values grows.

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

Pattern observation: The work grows directly with the number of items.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows in a straight line with the number of input items.

Common Mistake

[X] Wrong: "Using BuildOptional or buildEither makes the code run instantly regardless of input size."

[OK] Correct: These builders only control which code runs, but if that code loops over many items, the time still grows with input size.

Interview Connect

Understanding how optional and conditional code affects time helps you explain your code's efficiency clearly and confidently.

Self-Check

What if the input array was replaced with a nested array? How would that change the time complexity?

Practice

1. What is the main purpose of buildOptional in Swift's result builders?

easy

A. To choose between two code paths explicitly

B. To wrap optional code blocks so they can be included or skipped

C. To force unwrap optionals in code blocks

D. To create loops inside result builders

Solution

1. Step 1: Understand buildOptional's role

   buildOptional is designed to handle optional code blocks, allowing them to be included if present or skipped if nil.

2. Step 2: Compare with other builder functions

   buildEither chooses between two paths, but buildOptional specifically wraps optional code, making it flexible for optional UI parts.

3. Final Answer:

   To wrap optional code blocks so they can be included or skipped -> Option B

4. Quick Check:

   buildOptional wraps optionals = B [OK]

Hint: Remember: buildOptional handles optionals, buildEither picks sides [OK]

Common Mistakes:

• Confusing buildOptional with buildEither
• Thinking buildOptional forces unwrapping
• Assuming buildOptional creates loops

2. Which of the following is the correct syntax to use buildEither for choosing the first branch in a Swift result builder?

easy

A. buildEither(option: 1) { Text("First") }

B. buildEither(second: { Text("First") })

C. buildEither(first: { Text("First") })

D. buildEither(branch: .first, content: { Text("First") })

Solution

1. Step 1: Recall buildEither syntax

   The correct syntax uses named parameters first or second to specify the branch.

2. Step 2: Identify the correct usage

   buildEither(first: { Text("First") }) uses buildEither(first: { ... }), which matches the official Swift syntax for choosing the first branch.

3. Final Answer:

   buildEither(first: { Text("First") }) -> Option C

4. Quick Check:

   buildEither first branch = A [OK]

Hint: Use named parameters first or second with buildEither [OK]

Common Mistakes:

• Using incorrect parameter names like option or branch
• Confusing first and second parameters
• Trying to pass branch as enum instead of named argument

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

enum ResultBuilder {
  static func buildEither(first: String) -> String { "First: \(first)" }
  static func buildEither(second: String) -> String { "Second: \(second)" }
}

let result = ResultBuilder.buildEither(first: "Hello")
print(result)

medium

A. Compilation error

B. Second: Hello

C. Hello

D. First: Hello

Solution

1. Step 1: Identify which buildEither is called

   The code calls buildEither(first: "Hello"), so the first overload is used.

2. Step 2: Understand the returned string

   The first overload returns the string "First: Hello" which is printed.

3. Final Answer:

   First: Hello -> Option D

4. Quick Check:

   buildEither first branch returns "First: Hello" = A [OK]

Hint: Check which named parameter is used: first or second [OK]

Common Mistakes:

• Assuming second branch runs when first is called
• Expecting just the input string without prefix
• Thinking this causes a compile error

4. Given this Swift code snippet, what is the error and how to fix it?

struct Builder {
  @resultBuilder
  struct MyBuilder {
    static func buildEither(first: String) -> String { first }
    static func buildEither(second: String) -> String { second }
  }
}

let value = Builder.MyBuilder.buildEither(third: "Oops")

medium

A. Error: No 'third' parameter; fix by using 'first' or 'second'

B. Error: Missing return statement; fix by adding return

C. Error: buildEither cannot be static; remove static keyword

D. No error; code runs fine

Solution

1. Step 1: Identify the method call

   The code calls buildEither(third: "Oops"), but only first and second parameters exist.

2. Step 2: Understand the fix

   To fix, replace third with either first or second to match the defined overloads.

3. Final Answer:

   Error: No 'third' parameter; fix by using 'first' or 'second' -> Option A

4. Quick Check:

   buildEither only accepts first or second = C [OK]

Hint: Use only first or second parameters with buildEither [OK]

Common Mistakes:

• Trying to add unsupported parameter names
• Ignoring static keyword requirements
• Assuming code runs without error

5. How can you use buildOptional and buildEither together to conditionally build a SwiftUI view that shows "Logged In" if a user is logged in, "Guest" if not logged in but guest mode is enabled, and nothing otherwise?

hard

A. Use buildOptional to wrap guest mode view, and buildEither to choose between logged in and guest

B. Use buildEither to wrap guest mode view, and buildOptional to choose between logged in and guest

C. Use only buildOptional for all conditions

D. Use only buildEither for all conditions

Solution

1. Step 1: Understand the conditions

   We have three cases: logged in, guest mode, and neither. buildEither can choose between logged in and guest mode views.

2. Step 2: Use buildOptional for the third case

   The third case (neither) means no view, so wrap the guest mode view in buildOptional to include it only if guest mode is enabled.

3. Step 3: Combine both builders

   Use buildEither to select logged in or guest mode, and buildOptional to skip guest mode if disabled, resulting in no view if neither condition is true.

4. Final Answer:

   Use buildOptional to wrap guest mode view, and buildEither to choose between logged in and guest -> Option A

5. Quick Check:

   buildOptional wraps optional guest, buildEither picks logged in or guest = D [OK]

Hint: buildEither picks branches; buildOptional skips optional parts [OK]

Common Mistakes:

• Using buildEither alone for optional skipping
• Using buildOptional alone for branching
• Not handling the 'no view' case properly