Swift version: 5.6
You should already know that Swift lets you specify a concrete type as a function parameter, meaning that you can say “this parameter must be a string.” Swift also lets you specify protocols types for function parameters, meaning that you can say “this parameter must conform to Codable
.”
Those two are straightforward, but sometimes you need more power. Fortunately, Swift lets us represent existentials of classes and subtypes that conform to protocols, which is dramatic way of saying that you can now refer to types in a more complex way.
As an example, consider this class hierarchy:
class Animal { }
class Dog: Animal, Codable { }
class Cat: Animal, Codable { }
There’s a main Animal
class, and two subclasses called Dog
and Cat
. Both of the subclasses also conform to Codable
. Swift lets us combine both Animal
(the class) and Codable
(the protocol) to write functions that require a parameter to be both at the same time:
func encodeAnimal(with animal: Animal & Codable) {
}
let animal = Dog()
encodeAnimal(with: animal)
Without the Codable
part that function would accept instances of the main Animal
class even though it wouldn’t work inside, and without the Animal
part that function would accept anything that’s Codable
– only the combination of the two makes sense.
SPONSORED Join a FREE crash course for mid/senior iOS devs who want to achieve an expert level of technical and practical skills – it’s the fast track to being a complete senior developer! Hurry up because it'll be available only until October 1st.
Sponsor Hacking with Swift and reach the world's largest Swift community!
Available from iOS 8.0
This is part of the Swift Knowledge Base, a free, searchable collection of solutions for common iOS questions.
Link copied to your pasteboard.