Why structs are preferred in Swift - Visual Breakdown

Concept Flow - Why structs are preferred in Swift

Define Struct

↓

Create Instance

↓

Copy Instance

↓

Modify Copy

↓

Original Unchanged

↓

Safe, Fast, Predictable

Structs in Swift are value types that get copied when assigned or passed, making them safe and predictable by avoiding shared state.

Execution Sample

Swift

struct Point {
  var x: Int
  var y: Int
}

var p1 = Point(x: 1, y: 2)
var p2 = p1
p2.x = 10

This code shows creating a struct instance, copying it, and modifying the copy without changing the original.

Execution Table

Step	Action	Variable State	Explanation
1	Define struct Point with x and y	No instances yet	Struct type is ready to use
2	Create p1 = Point(x:1, y:2)	p1: (x=1, y=2)	p1 holds a Point with x=1, y=2
3	Assign p2 = p1 (copy)	p1: (x=1, y=2), p2: (x=1, y=2)	p2 is a copy of p1, separate memory
4	Modify p2.x = 10	p1: (x=1, y=2), p2: (x=10, y=2)	Changing p2 does not affect p1
5	Check p1.x	p1.x = 1	Original p1 remains unchanged
6	Check p2.x	p2.x = 10	Modified copy reflects new value

💡 Execution stops after demonstrating that modifying a struct copy does not change the original instance.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
p1	undefined	(x=1, y=2)	(x=1, y=2)	(x=1, y=2)	(x=1, y=2)
p2	undefined	undefined	(x=1, y=2)	(x=10, y=2)	(x=10, y=2)

Key Moments - 3 Insights

Why does changing p2.x not affect p1.x?

Because structs are value types, assigning p1 to p2 copies the data. So p2 is independent, as shown in step 4 and 5 of the execution_table.

What happens when we assign one struct variable to another?

A full copy of the struct is made, not a reference. This is why p2 gets its own copy in step 3.

Why are structs considered safer than classes in Swift?

Structs avoid shared mutable state because each copy is independent, preventing unexpected changes. This is demonstrated by p1 and p2 having different values after modification.

Visual Quiz - 3 Questions

Look at the execution_table at step 4, what is the value of p1.x?

A 10

B 1

C Undefined

D 0

💡 Hint

Check the Variable State column at step 4 where p1.x remains unchanged.

At which step does p2 get its own copy of p1?

A Step 3

B Step 2

C Step 4

D Step 5

💡 Hint

Look at the Action column where p2 is assigned from p1.

If structs were reference types, what would happen when p2.x is changed?

A p1.x would stay the same

B p2.x would revert to original

C p1.x would also change

D p2.x would become undefined

💡 Hint

Think about shared references vs copies shown in variable_tracker.

Concept Snapshot

Swift structs are value types.
Assigning a struct copies its data.
Modifying a copy does not affect the original.
This makes structs safe and predictable.
Preferred for simple data models and thread safety.

Full Transcript

This visual execution shows why Swift prefers structs. Structs are value types, meaning when you assign one struct variable to another, it copies the data instead of sharing it. For example, when we create p1 as a Point struct and then assign p2 = p1, p2 gets its own copy. Changing p2.x does not change p1.x. This behavior avoids bugs from shared state and makes code safer and easier to understand. The execution table traces each step, showing variable states and actions. Key moments clarify common confusions about copying and independence of structs. The quiz tests understanding of these concepts by referencing the execution steps and variable changes.

Practice

1. Why are structs preferred over classes in Swift for small data types?

easy

A. Because structs allow inheritance and polymorphism

B. Because structs use more memory than classes

C. Because structs copy data, avoiding unexpected changes from shared references

D. Because structs require manual memory management

Solution

1. Step 1: Understand data copying in structs

   Structs in Swift create a copy of data when assigned or passed, so changes to one copy don't affect others.

2. Step 2: Compare with classes and shared references

   Classes use references, so multiple variables can point to the same data, causing unexpected changes.

3. Final Answer:

   Because structs copy data, avoiding unexpected changes from shared references -> Option C

4. Quick Check:

   Structs copy data = safer small data types [OK]

Hint: Structs copy data; classes share references [OK]

Common Mistakes:

• Thinking structs support inheritance like classes
• Believing structs use more memory than classes
• Assuming structs require manual memory management

2. Which of the following is the correct way to define a struct in Swift?

easy

A. struct Person { var name: String }

B. class Person { var name: String }

C. struct Person = (name: String)

D. struct Person: String { var name }

Solution

1. Step 1: Recall Swift struct syntax

   Structs are defined using the keyword struct followed by the name and curly braces containing properties.

2. Step 2: Check each option

   struct Person { var name: String } correctly uses struct Person { var name: String }. class Person { var name: String } uses class, not struct. Options C and D have invalid syntax.

3. Final Answer:

   struct Person { var name: String } -> Option A

4. Quick Check:

   Correct struct syntax = struct Person { var name: String } [OK]

Hint: Use 'struct Name { var property: Type }' for structs [OK]

Common Mistakes:

• Using 'class' keyword instead of 'struct'
• Incorrect property declaration syntax
• Trying to assign struct like a tuple

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

struct Point { var x: Int; var y: Int }
var p1 = Point(x: 5, y: 10)
var p2 = p1
p2.x = 20
print(p1.x)

medium

A. 5

B. 20

C. 10

D. Compilation error

Solution

1. Step 1: Understand struct copying behavior

   Assigning p1 to p2 copies the data. They are independent after assignment.

2. Step 2: Analyze the change to p2.x

   Changing p2.x to 20 does not affect p1.x, which remains 5.

3. Final Answer:

   5 -> Option A

4. Quick Check:

   Struct copy means p1.x stays 5 [OK]

Hint: Struct assignment copies data; original stays unchanged [OK]

Common Mistakes:

• Thinking p1.x changes when p2.x changes
• Confusing structs with class reference behavior
• Expecting runtime error due to assignment

4. Identify the error in this Swift code using structs:

struct Rectangle {
  var width: Int
  var height: Int
}

var rect1 = Rectangle(width: 10, height: 20)
var rect2 = rect1
rect2.width = 30
print(rect1.width)

medium

A. rect2.width cannot be changed because structs are immutable

B. rect1.width prints 30 because structs share references

C. Compilation error due to missing initializer

D. No error; rect1.width prints 10 because structs copy data

Solution

1. Step 1: Check mutability of struct instances

   Since rect2 is a variable (var), its properties can be changed.

2. Step 2: Understand copying behavior

   Assigning rect1 to rect2 copies the data. Changing rect2.width does not affect rect1.width.

3. Final Answer:

   No error; rect1.width prints 10 because structs copy data -> Option D

4. Quick Check:

   Struct copy means rect1.width stays 10 [OK]

Hint: Structs copy data; changing copy doesn't affect original [OK]

Common Mistakes:

• Assuming structs are immutable by default
• Thinking structs share references like classes
• Expecting compilation error for missing initializer

5. You want to create a simple data type to store a user's profile with name and age. Why is using a struct better than a class in Swift for this case?

hard

A. Structs use reference counting, improving performance for user data

B. Structs provide automatic copying, preventing accidental shared changes in user data

C. Structs allow inheritance, making it easier to extend user profiles

D. Structs require manual memory management, giving more control over user data

Solution

1. Step 1: Consider data safety for user profiles

   User profiles are simple data that should not change unexpectedly when copied or passed around.

2. Step 2: Compare structs and classes for this use

   Structs copy data automatically, so each copy is independent, avoiding bugs from shared references common in classes.

3. Final Answer:

   Structs provide automatic copying, preventing accidental shared changes in user data -> Option B

4. Quick Check:

   Struct copy = safer user profile data [OK]

Hint: Use structs for simple data to avoid shared reference bugs [OK]

Common Mistakes:

• Thinking structs support inheritance like classes
• Confusing reference counting with copying
• Believing structs require manual memory management