Why structs are preferred in Swift - Performance Analysis

Time Complexity: Why structs are preferred in Swift

O(n)

Understanding Time Complexity

When we choose between structs and classes in Swift, it helps to understand how their performance changes as data grows.

We want to see how the cost of using structs scales compared to classes.

Scenario Under Consideration

Analyze the time complexity of copying a struct versus a class instance.

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

let p1 = Point(x: 10, y: 20)
let p2 = p1 // Copy of struct

class Circle {
  var radius: Int
  init(radius: Int) { self.radius = radius }
}

let c1 = Circle(radius: 5)
let c2 = c1 // Reference to same class instance

This code shows copying a struct creates a new copy, while copying a class just copies a reference.

Identify Repeating Operations

Look at what happens when copying data:

• Primary operation: Copying all stored properties in the struct.
• How many times: Once per copy operation, proportional to the size of the struct.

How Execution Grows With Input

As the struct grows larger, copying takes more time because all data is duplicated.

Input Size (n)	Approx. Operations
10	10 copies of properties
100	100 copies of properties
1000	1000 copies of properties

Pattern observation: Copying time grows linearly with the size of the struct.

Final Time Complexity

Time Complexity: O(n)

This means copying a struct takes time proportional to its size, growing steadily as the data grows.

Common Mistake

[X] Wrong: "Copying a struct is always slower than using a class because it duplicates data every time."

[OK] Correct: For small structs, copying is very fast and often cheaper than managing references and memory for classes.

Interview Connect

Understanding how structs copy data helps you explain why Swift prefers structs for safety and performance in many cases.

Self-Check

"What if the struct contains a large array? How would copying affect time complexity then?"

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