Type constraints with protocol conformance in Swift - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a generic function that accepts any type conforming to the Comparable protocol.

Swift

func findMax<T: [1]>(_ a: T, _ b: T) -> T {
    return a > b ? a : b
}

Drag options to blanks, or click blank then click option'

ACodable

BComparable

CEquatable

DHashable

Attempts:

3 left

💡 Hint

Common Mistakes

Using Equatable instead of Comparable, which only supports equality checks.

Using Codable or Hashable which do not provide comparison operators.

The generic type T must conform to Comparable to use the > operator.

2fill in blank

medium

Complete the code to constrain the generic type to the Hashable protocol.

Swift

func checkAndHash<T: [1]>(_ value: T) -> Int {
    return value.hashValue
}

Drag options to blanks, or click blank then click option'

AHashable

BCodable

CComparable

DEquatable

Attempts:

3 left

💡 Hint

Common Mistakes

Using Equatable instead of Hashable, as Equatable lacks hashValue.

Using Codable or Comparable which do not provide hashValue.

The generic type T must conform to Hashable to use hashValue. Hashable inherits from Equatable.

3fill in blank

hard

Fix the error in the generic function declaration by filling the correct protocol conformance.

Swift

func compareItems<T: [1]>(_ first: T, _ second: T) -> Bool {
    return first == second
}

Drag options to blanks, or click blank then click option'

ACodable

BComparable

CEquatable

DHashable

Attempts:

3 left

💡 Hint

Common Mistakes

Using Comparable which supports ordering but not just equality.

Using Codable or Hashable which do not define == operator.

The equality operator == requires the type to conform to Equatable.

4fill in blank

hard

Fill both blanks to declare a generic function where T conforms to Codable and U conforms to Hashable.

Swift

func processItems<T: [1], U: [2]>(item1: T, item2: U) {
    print(item1)
    print(item2.hashValue)
}

Drag options to blanks, or click blank then click option'

ACodable

BEquatable

CHashable

DComparable

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up the protocols for T and U.

Using Comparable or Equatable incorrectly.

The first generic type T conforms to Codable, and the second generic type U must conform to Hashable to access hashValue.

5fill in blank

hard

Fill all three blanks to create a generic function where T conforms to Comparable, U conforms to Equatable, and V conforms to Codable.

Swift

func genericFunction<T: [1], U: [2], V: [3]>(a: T, b: U, c: V) {
    if a > a {
        print(b == b)
    }
    print(c)
}

Drag options to blanks, or click blank then click option'

AComparable

BEquatable

CCodable

DHashable

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing which protocol supports which operator.

Using Hashable instead of Codable for printing.

The generic type T must conform to Comparable to use >. U must conform to Equatable to use ==. V conforms to Codable.

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