Why Extending built-in types in Swift? - Purpose & Use Cases

The Big Idea

What if you could teach numbers and strings new tricks, just like your own custom tools?

The Scenario

Imagine you want to add a new feature to a number or a string in your program, like making a number tell if it's even or odd, but the built-in number type doesn't have that feature.

You try to write separate functions everywhere to check this, but it feels messy and repetitive.

The Problem

Writing separate functions for every new feature is slow and confusing.

You have to remember to call the right function each time, and it's easy to make mistakes or forget.

Your code becomes long and hard to read because the new features don't feel like they belong to the numbers or strings themselves.

The Solution

Extending built-in types lets you add new features directly to existing types like numbers or strings.

This means you can call your new features just like the built-in ones, making your code cleaner and easier to understand.

Before vs After

✗ Before

func isEven(_ number: Int) -> Bool {
    return number % 2 == 0
}

let result = isEven(4)

✓ After

extension Int {
    var isEven: Bool {
        return self % 2 == 0
    }
}

let result = 4.isEven

What It Enables

You can make your code more natural and expressive by adding your own features to existing types.

Real Life Example

Imagine adding a feature to the String type that tells if a password is strong, so you can just write password.isStrong instead of calling a separate function.

Key Takeaways

Manual functions for new features are repetitive and messy.

Extending built-in types adds features directly to existing types.

This makes code cleaner, easier to read, and more natural.

Practice

1. What is the main purpose of extending built-in types in Swift?

easy

A. To change the stored properties of existing types

B. To delete existing methods from built-in types

C. To add new methods or computed properties to existing types

D. To create subclasses of built-in types

Solution

1. Step 1: Understand what extensions do

   Extensions allow adding new methods or computed properties to existing types without subclassing.

2. Step 2: Identify what extensions cannot do

   Extensions cannot add stored properties or delete existing methods.

3. Final Answer:

   To add new methods or computed properties to existing types -> Option C

4. Quick Check:

   Extensions add methods/properties = B [OK]

Hint: Remember: extensions add features, not stored data [OK]

Common Mistakes:

• Thinking extensions can add stored properties
• Confusing extensions with subclassing
• Believing extensions can remove methods

2. Which of the following is the correct syntax to extend the built-in Int type with a method isEven() that returns a Bool?

easy

A. extension Int { func isEven() -> Bool { return self % 2 == 0 } }

B. extend Int { func isEven() -> Bool { return self % 2 == 0 } }

C. extension Int { func isEven { return self % 2 == 0 } }

D. extension Int { isEven() -> Bool { return self % 2 == 0 } }

Solution

1. Step 1: Identify the correct keyword for extension

   Swift uses the keyword extension to add methods to existing types.

2. Step 2: Check method syntax

   The method must have parentheses and a return type: func isEven() -> Bool. The body uses self % 2 == 0.

3. Final Answer:

   extension Int { func isEven() -> Bool { return self % 2 == 0 } } -> Option A

4. Quick Check:

   Correct extension syntax = D [OK]

Hint: Use 'extension' keyword and full method signature [OK]

Common Mistakes:

• Using 'extend' instead of 'extension'
• Omitting parentheses in method declaration
• Missing 'func' keyword before method name

3. Consider this Swift code:

extension String {
    func reversedString() -> String {
        return String(self.reversed())
    }
}

let word = "hello"
print(word.reversedString())

What is the output when this code runs?

medium

A. Error: reversed() not found

B. hello

C. nil

D. olleh

Solution

1. Step 1: Understand the extension method

   The method reversedString() returns a new String made by reversing the characters of the original string.

2. Step 2: Apply method to 'hello'

   Reversing "hello" results in "olleh".

3. Final Answer:

   olleh -> Option D

4. Quick Check:

   String reversed = olleh [OK]

Hint: Remember reversed() returns characters reversed [OK]

Common Mistakes:

• Expecting original string output
• Thinking reversed() returns an error
• Confusing reversed() with reverse()

4. What is wrong with this Swift extension code?

extension Double {
    var squared: Double {
        return self * self
    }

    var storedValue: Double = 0.0
}

medium

A. Extensions cannot add stored properties like 'storedValue'

B. Computed properties must use 'func' keyword

C. The 'squared' property must be a method, not a property

D. The extension must be declared as 'class extension'

Solution

1. Step 1: Review extension property rules

   Extensions can add computed properties but cannot add stored properties.

2. Step 2: Identify the stored property

   The line var storedValue: Double = 0.0 tries to add a stored property, which is not allowed.

3. Final Answer:

   Extensions cannot add stored properties like 'storedValue' -> Option A

4. Quick Check:

   No stored properties in extensions = A [OK]

Hint: Remember: only computed properties allowed in extensions [OK]

Common Mistakes:

• Trying to add stored properties in extensions
• Confusing computed properties with stored properties
• Thinking extensions require 'class' keyword

5. You want to extend the built-in Array type in Swift to add a method secondElement() that returns the second element if it exists, or nil otherwise. Which of the following extensions correctly implements this?

hard

A. extension Array {
func secondElement() -> Element {
return self[1]
}
}

B. extension Array {
func secondElement() -> Element? {
return self.count > 1 ? self[1] : nil
}
}

C. extension Array {
var secondElement: Element? {
if self.count >= 2 { return self[2] } else { return nil }
}
}

D. extension Array {
func secondElement() -> Element? {
if self.count > 0 { return self[1] } else { return nil }
}
}

Solution

1. Step 1: Check method signature and return type

   The method should return an optional Element (Element?) because the second element might not exist.

2. Step 2: Verify index and condition

   Arrays are zero-indexed, so the second element is at index 1. The condition should check if count > 1 to safely access index 1.

3. Step 3: Compare options

   The correct one uses ternary operator: return self.count > 1 ? self[1] : nil. The non-optional return crashes on short arrays. The computed property uses index 2 (third element). The if-else checks count > 0, allowing index 1 access when count == 1, causing runtime crash.

4. Final Answer:

   extension Array { func secondElement() -> Element? { return self.count > 1 ? self[1] : nil } } -> Option B

5. Quick Check:

   Safe optional return with index 1 = A [OK]

Hint: Check array count > 1 and return optional Element [OK]

Common Mistakes:

• Accessing wrong index (like 2 instead of 1)
• Returning non-optional Element causing crash
• Using computed property but with wrong index