Type constraints with protocol conformance in Swift - Step-by-Step Execution

Concept Flow - Type constraints with protocol conformance

Define Protocol

↓

Define Generic Function

↓

Add Type Constraint: T: Protocol

↓

Call Function with Type

↓

Check if Type conforms to Protocol

Yes No↓

Execute Function

↓

Return Result

This flow shows how a generic function requires its type to follow a protocol, allowing safe use of protocol methods inside the function.

Execution Sample

Swift

protocol Greetable {
    func greet() -> String
}

func welcome<T: Greetable>(_ person: T) -> String {
    return person.greet()
}

Defines a protocol and a generic function that only accepts types conforming to that protocol, then calls the protocol method.

Execution Table

Step	Action	Type Used	Check Protocol Conformance	Result	Output
1	Define protocol Greetable	-	-	Protocol created	-
2	Define generic function welcome with constraint T: Greetable	-	-	Function created	-
3	Call welcome with type Person	Person	Person conforms to Greetable?	Yes	-
4	Inside welcome, call person.greet()	Person	-	Method called	"Hello!"
5	Return from welcome	Person	-	Return value	"Hello!"
6	Call welcome with type Int	Int	Int conforms to Greetable?	No	Compile error

💡 Execution stops if type does not conform to protocol, causing compile error.

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
person	undefined	Person instance	Person instance	Person instance
Output	undefined	undefined	"Hello!"	"Hello!"

Key Moments - 2 Insights

Why does calling welcome with Int cause an error?

Because Int does not conform to the Greetable protocol, the type constraint T: Greetable fails, as shown in execution_table step 6.

Can we call greet() inside welcome without the type constraint?

No, without T: Greetable, the compiler cannot guarantee the method greet() exists on T, so it will cause a compile error.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output after calling welcome with a Person?

A "Hi!"

B "Hello!"

C Compile error

D No output

💡 Hint

Check step 4 and 5 in the execution_table where person.greet() returns "Hello!"

At which step does the compiler check if the type conforms to the protocol?

A Step 3

B Step 4

C Step 2

D Step 6

💡 Hint

Look at execution_table step 3 where the conformance check happens before function execution

If we remove the constraint T: Greetable, what happens when calling welcome with Person?

A It compiles and runs fine

B Runtime error

C Compile error because greet() is unknown

D Person is treated as Any

💡 Hint

Refer to key_moments about why the constraint is needed to call greet() safely

Concept Snapshot

Syntax:
func functionName<T: ProtocolName>(_ param: T) { ... }

Behavior:
- T must conform to ProtocolName
- Inside function, protocol methods are accessible

Key rule:
- Compiler enforces conformance at call time
- Non-conforming types cause compile errors

Full Transcript

This visual trace shows how Swift uses type constraints with protocol conformance in generic functions. First, a protocol named Greetable is defined with a greet() method. Then, a generic function welcome requires its type T to conform to Greetable. When calling welcome with a Person type that conforms to Greetable, the function calls greet() successfully and returns "Hello!". If we try to call welcome with a type like Int that does not conform, the compiler stops with an error. The variable tracker shows how the person variable holds the instance and the output is the greeting string. Key moments clarify why the constraint is necessary and what happens if it is missing. The quiz questions test understanding of output, conformance checks, and the role of constraints. This helps beginners see step-by-step how Swift ensures safe use of protocol methods in generics.