📖 Scenario: You are building a simple app that works with collections of numbers. You want to add a new feature to calculate the sum of all elements, but only for collections that hold numbers.
🎯 Goal: Create an extension with constraints to add a sumElements() method to collections of numbers.
📋 What You'll Learn
Create an array of integers called numbers with the values [3, 7, 2, 9].
Create a constant called isNonEmpty that checks if numbers is not empty.
Write an extension for Collection where the element type is Int to add a method sumElements() that returns the sum of all elements.
Print the result of calling sumElements() on numbers.
💡 Why This Matters
🌍 Real World
Extensions with constraints let you add useful features to existing types only when they meet certain conditions, like holding numbers. This helps keep your code safe and organized.
💼 Career
Understanding how to write constrained extensions is important for Swift developers to create reusable and type-safe code, a common task in app development.
Progress0 / 4 steps
1
Create the initial array
Create an array called numbers with the exact values [3, 7, 2, 9].
Swift
Hint
Use let numbers = [3, 7, 2, 9] to create the array.
2
Add a configuration constant
Create a constant called isNonEmpty that is true if numbers is not empty, otherwise false.
Swift
Hint
Use !numbers.isEmpty to check if the array is not empty.
3
Write the extension with constraints
Write an extension for Collection where the element type is Int. Add a method called sumElements() that returns the sum of all elements using reduce(0, +).
Swift
Hint
Use extension Collection where Element == Int and reduce(0, +) inside sumElements().
4
Print the sum of elements
Print the result of calling sumElements() on the numbers array.
Swift
Hint
Use print(numbers.sumElements()) to display the sum.
Practice
(1/5)
1. What is the main purpose of using where in Swift extensions with constraints?
easy
A. To override existing methods in a class
B. To create a new class from an existing one
C. To add functionality only to types that meet specific conditions
D. To declare a variable inside an extension
Solution
Step 1: Understand the role of where in extensions
The where keyword is used to specify conditions that types must meet to gain the added functionality.
Step 2: Recognize the purpose of constraints
Constraints ensure that only types matching the condition get the new methods or properties, keeping code safe and organized.
Final Answer:
To add functionality only to types that meet specific conditions -> Option C
Quick Check:
Extensions with where add features conditionally = A [OK]
Hint: Remember: where limits extension to certain types [OK]
Common Mistakes:
Thinking where creates new classes
Confusing extensions with inheritance
Using where to declare variables
2. Which of the following is the correct syntax to extend Array only when its elements conform to the Equatable protocol?
easy
A. extension Array where Element == Equatable { }
B. extension Array if Element == Equatable { }
C. extension Array with Element: Equatable { }
D. extension Array where Element: Equatable { }
Solution
Step 1: Recall correct syntax for constrained extensions
Swift uses where followed by the condition, e.g., Element: Equatable to constrain extensions.
Step 2: Identify the correct option
extension Array where Element: Equatable { } uses the correct syntax: extension Array where Element: Equatable { }. Others misuse if, ==, or with.
Final Answer:
extension Array where Element: Equatable { } -> Option D
Quick Check:
Use where and colon for protocol conformance = C [OK]
Hint: Use where Type: Protocol for constraints [OK]
Common Mistakes:
Using == instead of : for protocol conformance
Replacing where with if
Writing with instead of where
3. What will be the output of this Swift code?
extension Collection where Element: Numeric {
func sum() -> Element {
reduce(0, +)
}
}
let numbers = [1, 2, 3, 4]
print(numbers.sum())
medium
A. 0
B. 10
C. Error: sum() not found
D. 1234
Solution
Step 1: Understand the extension constraint
The extension adds a sum() method only to collections whose elements conform to Numeric. Array of Int fits this.
Step 2: Calculate the sum of the array
The sum() method uses reduce(0, +) which adds all elements: 1+2+3+4 = 10.
Final Answer:
10 -> Option B
Quick Check:
Sum of [1,2,3,4] = 10 [OK]
Hint: Check if element type matches constraint to use extension methods [OK]
Common Mistakes:
Assuming sum() works on non-Numeric elements
Thinking sum() concatenates numbers
Ignoring the extension constraint
4. Identify the error in this Swift extension:
extension Array where Element == Int {
func multiplyAll() -> Int {
reduce(1, *)
}
}
medium
A. reduce(1, *) is invalid syntax
B. Cannot use == to check type equality in extension constraints
C. Missing return keyword in multiplyAll()
D. Array cannot be extended with constraints
Solution
Step 1: Check extension constraint syntax
Swift requires Element: SomeProtocol or Element == SomeType is valid only for type equality, but for generic parameters, Element == Int is allowed.
Step 2: Verify if Element == Int is valid here
Actually, Element == Int is valid syntax for type equality constraints in extensions, so Cannot use == to check type equality in extension constraints is incorrect.
Step 3: Check other options
Missing return keyword in multiplyAll(): The function uses implicit return allowed in single-expression functions, so no error. reduce(1, *) is invalid syntax: reduce(1, *) is invalid syntax because the operator * cannot be passed as a bare argument like that. Array cannot be extended with constraints: Arrays can be extended with constraints.
Step 4: Re-examine Cannot use == to check type equality in extension constraints
In Swift 5+, Element == Int is valid. So no syntax error here.
Final Answer:
reduce(1, *) is invalid syntax -> Option A
Quick Check:
Operator * must be passed as a closure or function, not bare = B [OK]
Hint: Remember: Element == Type is valid for type equality [OK]
Common Mistakes:
Thinking == is invalid in extension constraints
Expecting explicit return in single-expression functions
Misreading reduce syntax
5. You want to add a method isAllEqual() to arrays only when their elements conform to Equatable. Which extension correctly implements this method to return true if all elements are equal, or false otherwise?
hard
A. extension Array where Element: Equatable {
func isAllEqual() -> Bool {
guard let first = self.first else { return true }
return allSatisfy { $0 == first }
}
}
B. extension Array where Element == Equatable {
func isAllEqual() -> Bool {
for i in 1..
C. extension Array where Element: Equatable {
func isAllEqual() -> Bool {
for element in self {
if element != self[0] { return false }
}
return true
}
}
D. extension Array {
func isAllEqual() -> Bool {
for i in 1..
Solution
Step 1: Check the extension constraint correctness
Only options A and C use where Element: Equatable, which is correct to add methods requiring equality checks.
Step 2: Analyze method implementation
extension Array where Element: Equatable {
func isAllEqual() -> Bool {
guard let first = self.first else { return true }
return allSatisfy { $0 == first }
}
} safely handles empty arrays by returning true and uses allSatisfy for clarity. extension Array where Element: Equatable {
func isAllEqual() -> Bool {
for element in self {
if element != self[0] { return false }
}
return true
}
} compares each element to self[0] but does not handle empty arrays, which can cause runtime error. extension Array where Element == Equatable {
func isAllEqual() -> Bool {
for i in 1..Element == Equatable which is invalid syntax. extension Array {
func isAllEqual() -> Bool {
for i in 1..
Final Answer:
Option A correctly implements isAllEqual() with proper constraint and safe code -> Option A
Quick Check:
Use where Element: Equatable and safe checks = A [OK]
Hint: Use where Element: Equatable and safe first element check [OK]
Common Mistakes:
Using Element == Equatable instead of Element: Equatable
Not handling empty arrays safely
Extending without constraints for Equatable methods
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.