Type constraints with protocol conformance in Swift - Mini Project: Build & Apply

Type constraints with protocol conformance

📖 Scenario: You are building a simple system to handle different shapes and calculate their areas. Each shape must follow a common rule to provide its area.

🎯 Goal: Create a protocol called Shape with a property for area. Then, create two structs that conform to this protocol. Finally, write a generic function that only accepts types conforming to Shape and prints their area.

📋 What You'll Learn

Create a protocol named Shape with a read-only property area of type Double

Create a struct Square that conforms to Shape with a sideLength property

Create a struct Circle that conforms to Shape with a radius property

Write a generic function printArea that accepts a parameter constrained to Shape and prints its area

💡 Why This Matters

🌍 Real World

Protocols and type constraints help write flexible and reusable code that works with many types sharing common behavior.

💼 Career

Understanding protocol conformance and generics is essential for Swift developers building scalable and maintainable apps.

1

Create the Shape protocol

Create a protocol called Shape with a read-only property area of type Double.

Swift

# Your code here

Hint

Protocols define a blueprint. Use var area: Double { get } to declare a read-only property.

2

Create Square and Circle structs conforming to Shape

Create a struct called Square with a sideLength property of type Double. Make it conform to Shape by implementing the area property as sideLength squared. Also, create a struct called Circle with a radius property of type Double. Make it conform to Shape by implementing the area property as π times radius squared.

Swift

protocol Shape {
    var area: Double { get }
}

# Your code here

Hint

Use struct Name: Shape to conform. Calculate area inside a computed property.

3

Write a generic function with type constraint

Write a generic function called printArea that accepts one parameter named shape of generic type T. Add a type constraint so that T must conform to the Shape protocol. Inside the function, print the area of the shape using print("Area: \(shape.area)").

Swift

protocol Shape {
    var area: Double { get }
}

struct Square: Shape {
    var sideLength: Double
    var area: Double {
        sideLength * sideLength
    }
}

struct Circle: Shape {
    var radius: Double
    var area: Double {
        Double.pi * radius * radius
    }
}

# Your code here

Hint

Use func printArea<T: Shape>(shape: T) to add the type constraint.

4

Call printArea with Square and Circle instances

Create a constant square of type Square with sideLength 4.0. Create a constant circle of type Circle with radius 3.0. Call printArea with square and then with circle.

Swift

protocol Shape {
    var area: Double { get }
}

struct Square: Shape {
    var sideLength: Double
    var area: Double {
        sideLength * sideLength
    }
}

struct Circle: Shape {
    var radius: Double
    var area: Double {
        Double.pi * radius * radius
    }
}

func printArea(shape: T) {
    print("Area: \(shape.area)")
}

# Your code here

Hint

Create instances with the exact property values and call printArea with them.

Practice

1. What does the syntax <T: ProtocolName> mean in Swift?

easy

A. It means type T must conform to ProtocolName.

B. It means type T inherits from ProtocolName.

C. It means ProtocolName is a subclass of T.

D. It means T is an instance of ProtocolName.

Solution

1. Step 1: Understand generic type constraints

   The syntax <T: ProtocolName> restricts T to types that conform to ProtocolName.

2. Step 2: Differentiate from inheritance and instances

   Protocols define requirements, not inheritance. T must implement ProtocolName, not inherit or be an instance.

3. Final Answer:

   It means type T must conform to ProtocolName. -> Option A

4. Quick Check:

   Type constraint = must conform [OK]

Hint: Remember: means T follows that protocol [OK]

Common Mistakes:

• Confusing protocol conformance with class inheritance
• Thinking T is an instance, not a type
• Mixing subclass and protocol concepts

2. Which of the following is the correct syntax to declare a generic function with a type constrained to the Equatable protocol?

easy

A. func compare(a: T, b: T) -> Bool {}

B. func compare(a: T, b: T) -> Bool {}

C. func compare(a: T, b: T) -> Bool {}

D. func compare<T>(a: T, b: T) -> Bool where T Equatable {}

Solution

1. Step 1: Recall correct generic constraint syntax

   The correct syntax uses <T: Equatable> to constrain T to Equatable.

2. Step 2: Identify syntax errors in other options

   A uses 'where' incorrectly inside angle brackets, B misses colon after T, D misplaces 'where' and lacks colon.

3. Final Answer:

   func compare<T: Equatable>(a: T, b: T) - correct syntax -> Option A

4. Quick Check:

   Use colon after T for protocol constraint [OK]

Hint: Use colon after T to add protocol constraint [OK]

Common Mistakes:

• Omitting colon ':' after generic type
• Misplacing 'where' clause
• Incorrect angle bracket usage

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

protocol Printable {
    func printValue()
}

struct Number: Printable {
    var value: Int
    func printValue() {
        print("Value is \(value)")
    }
}

func show(_ item: T) {
    item.printValue()
}

let num = Number(value: 10)
show(num)

medium

A. Compile error: Missing protocol conformance

B. Value is num

C. Value is 10

D. Runtime error

Solution

1. Step 1: Check protocol conformance

   Number struct conforms to Printable and implements printValue() correctly.

2. Step 2: Analyze function call

   show() accepts any Printable type; passing Number instance calls printValue(), printing "Value is 10".

3. Final Answer:

   Value is 10 -> Option C

4. Quick Check:

   Protocol method called prints value [OK]

Hint: Check if type implements protocol method before calling [OK]

Common Mistakes:

• Assuming protocol methods are optional
• Forgetting to implement protocol methods
• Confusing print output with variable name

4. Identify the error in this Swift code snippet:

protocol Describable {
    func describe() -> String
}

func printDescription<T>(item: T) where T: Describable {
    print(item.describe())
}

struct Person {
    var name: String
}

let p = Person(name: "Alice")
printDescription(item: p)

medium

A. Missing return type in describe() method

B. Function printDescription is missing parameter label

C. Generic constraint syntax is incorrect

D. Person does not conform to Describable protocol

Solution

1. Step 1: Check protocol conformance of Person

   Person struct does not declare conformance to Describable or implement describe().

2. Step 2: Understand generic constraint usage

   printDescription requires T to conform to Describable; passing Person causes compile error.

3. Final Answer:

   Person does not conform to Describable protocol -> Option D

4. Quick Check:

   Type must conform to protocol to satisfy constraint [OK]

Hint: Check if type implements protocol before passing to constrained function [OK]

Common Mistakes:

• Assuming protocol conformance is automatic
• Ignoring missing method implementations
• Misreading generic constraint syntax

5. Given two protocols:

protocol Identifiable {
    var id: String { get }
}
protocol Nameable {
    var name: String { get }
}

How do you declare a generic function that accepts a type conforming to both Identifiable and Nameable?

hard

A. func process(_ item: T) {}

B. Both C and D are correct

C. func process<T>(item: T) where T: Identifiable, T: Nameable {}

D. func process(_ item: T) {}

Solution

1. Step 1: Understand multiple protocol constraints syntax

   Swift allows multiple constraints using & inside angle brackets or multiple where clauses.

2. Step 2: Analyze options

   func process(_ item: T) {} uses & syntax correctly. func process<T>(item: T) where T: Identifiable, T: Nameable {} uses where clause with multiple constraints correctly. func process(_ item: T) {} is invalid syntax.

3. Final Answer:

   Both func process<T: Identifiable & Nameable> and func process<T> where T: Identifiable, T: Nameable are correct -> Option B

4. Quick Check:

   Multiple constraints: & or where clause [OK]

Hint: Use & or where clause for multiple protocol constraints [OK]

Common Mistakes:

• Using comma inside angle brackets incorrectly
• Confusing syntax for multiple constraints
• Forgetting to repeat T in where clause