Type erasure helps when protocols have associated types or self requirements that prevent direct use.
It adds a small performance cost due to indirection but improves code flexibility.
Summary
Type erasure hides specific types behind a common interface.
It allows storing and using different types uniformly.
It is useful for protocols with associated types or complex generics.
Practice
(1/5)
1. What is the main purpose of type erasure in Swift?
easy
A. To convert classes into structs automatically
B. To create new types from existing ones
C. To improve runtime performance by avoiding protocols
D. To hide specific types behind a common interface
Solution
Step 1: Understand type erasure concept
Type erasure is used to hide the concrete underlying type and expose a common interface.
Step 2: Identify the main purpose
This allows different types to be used uniformly without exposing their specific details.
Final Answer:
To hide specific types behind a common interface -> Option D
Quick Check:
Type erasure = hiding types behind interface [OK]
Hint: Type erasure hides types to unify usage [OK]
Common Mistakes:
Confusing type erasure with type conversion
Thinking it improves performance directly
Assuming it creates new types
2. Which of the following is the correct syntax to create a type-erased wrapper for a protocol MyProtocol?
easy
A. struct AnyMyProtocol: MyProtocol { private let _base: any MyProtocol }
B. struct AnyMyProtocol<T>: MyProtocol { private let _base: T }
C. struct AnyMyProtocol: MyProtocol { private let _base: MyProtocol }
D. struct AnyMyProtocol: MyProtocol { private let _base: some MyProtocol }
Solution
Step 1: Recall type erasure syntax
Type erasure uses a struct that conforms to the protocol and stores an instance of any Protocol to hide the concrete type.
Step 2: Identify correct syntax
struct AnyMyProtocol: MyProtocol { private let _base: any MyProtocol } uses any MyProtocol which is the correct way to store an existential type in Swift 5.7+.
Final Answer:
struct AnyMyProtocol: MyProtocol { private let _base: any MyProtocol } -> Option A
Quick Check:
Use any Protocol for type erasure storage [OK]
Hint: Use 'any Protocol' to store erased type [OK]
B. Cannot assign generic method to closure with Any parameter
C. Cannot use associatedtype in protocol
D. Function printItem has wrong return type
Solution
Step 1: Analyze closure assignment
The closure _print expects (Any) -> Void but printer.printItem expects (P.Item) -> Void, which is a mismatch.
Step 2: Understand type erasure limitation
Associated types prevent direct assignment because the types differ; you cannot assign a generic method to a closure with Any parameter.
Final Answer:
Cannot assign generic method to closure with Any parameter -> Option B
Quick Check:
Generic method ≠ closure with Any parameter [OK]
Hint: Generic methods can't be assigned to Any closures directly [OK]
Common Mistakes:
Thinking protocol conformance is missing
Confusing associatedtype usage
Assuming return type mismatch
5. You want to create a type-erased wrapper for a protocol DataSource with an associated type Item and a method func fetch() -> [Item]. Which approach correctly applies type erasure to allow storing different DataSource implementations in a single array?
hard
A. Create a struct AnyDataSource with a private closure _fetch: () -> [Any] and cast results inside
B. Use a generic struct AnyDataSource<T> storing DataSource directly
C. Create a struct AnyDataSource with a private closure _fetch: () -> [Item] and use type erasure with a generic initializer
D. Use protocol inheritance to remove associated type
Solution
Step 1: Understand associated type challenge
Protocols with associated types cannot be used directly in collections because the type varies.
Step 2: Apply type erasure pattern
Create a struct with a private closure returning [Item], and initialize it generically to wrap any DataSource, hiding the concrete type.
Step 3: Evaluate options
Create a struct AnyDataSource with a private closure _fetch: () -> [Item] and use type erasure with a generic initializer correctly uses a generic initializer and closure with [Item], preserving type safety and enabling storage in arrays.
Final Answer:
Create a struct AnyDataSource with a private closure _fetch: () -> [Item] and use type erasure with a generic initializer -> Option C
Quick Check:
Type erasure with generic init and closure = Create a struct AnyDataSource with a private closure _fetch: () -> [Item] and use type erasure with a generic initializer [OK]
Hint: Use generic init and closure returning [Item] for erasure [OK]
Common Mistakes:
Casting to [Any] loses type safety
Using generic struct prevents uniform storage
Trying to remove associated type via inheritance
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.