Structs vs classes in iOS Swift - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a struct named Person with a name property.

iOS Swift

struct Person {
  var [1]: String
}

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

Aname

Bage

Cheight

Dweight

Attempts:

3 left

💡 Hint

Common Mistakes

Using unrelated property names like age or height.

The property to store the person's name should be called name.

2fill in blank

medium

Complete the code to create an instance of the Person struct named person1.

iOS Swift

let person1 = [1](name: "Alice")

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

Astruct

Bclass

CPerson

Dvar

Attempts:

3 left

💡 Hint

Common Mistakes

Using keywords like class or var instead of the struct name.

To create an instance of a struct, use its name Person followed by parentheses.

3fill in blank

hard

Fix the error in the code by choosing the correct keyword to define a class named Animal.

iOS Swift

[1] Animal {
  var species: String
}

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

Aclass

Bfunc

Cstruct

Dlet

Attempts:

3 left

💡 Hint

Common Mistakes

Using struct or func instead of class.

Classes are defined using the keyword class in Swift.

4fill in blank

hard

Fill both blanks to complete the code that shows how classes support inheritance but structs do not.

iOS Swift

class Dog: [1] {
  var breed: String
  init(breed: String) {
    self.breed = breed
  }
}

struct [2] {
  var color: String
}

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

AAnimal

BPerson

CCar

DDog

Attempts:

3 left

💡 Hint

Common Mistakes

Using struct names that imply inheritance or using wrong base class names.

The class Dog inherits from the class Animal. Structs like Car cannot inherit.

5fill in blank

hard

Fill all three blanks to complete the code that demonstrates value type behavior of structs and reference type behavior of classes.

iOS Swift

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

var p1 = Point(x: 0, y: 0)
var p2 = p1
p2.x = [1]

class Location {
  var name: String
  init(name: String) {
    self.name = name
  }
}

var loc1 = Location(name: "Home")
var loc2 = loc1
loc2.name = [2]

print(p1.x) // [3]

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

A10

B"Work"

C0

D"Home"

Attempts:

3 left

💡 Hint

Common Mistakes

Thinking structs behave like classes and share references.

Changing p2.x does not affect p1.x because structs are value types. So p1.x remains 0. Changing loc2.name changes loc1.name because classes are reference types.

Practice

1. Which statement correctly describes the difference between struct and class in Swift?

easy

A. class is copied on assignment but struct is shared.

B. struct is a value type and class is a reference type.

C. struct supports inheritance but class does not.

D. struct can only have stored properties, class cannot.

Solution

1. Step 1: Understand value vs reference types

   In Swift, struct is a value type, meaning it is copied when assigned or passed around. class is a reference type, meaning instances share the same reference.

2. Step 2: Evaluate each option

   struct is a value type and class is a reference type. correctly states the difference. struct supports inheritance but class does not. is wrong because struct does not support inheritance. class is copied on assignment but struct is shared. reverses the behavior. struct can only have stored properties, class cannot. is false because class can have stored properties.

3. Final Answer:

   struct is a value type and class is a reference type. -> Option B

4. Quick Check:

   Value type = struct, Reference type = class [OK]

Hint: Remember: structs copy, classes share references [OK]

Common Mistakes:

• Confusing value and reference types
• Thinking structs support inheritance
• Assuming classes are copied on assignment

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

easy

A. class Person { var name: String }

B. struct Person: String { var name }

C. struct Person = { var name: String }

D. struct Person { var name: String }

Solution

1. Step 1: Recall Swift struct syntax

   A struct is declared with the keyword struct, followed by the name and curly braces containing properties.

2. Step 2: Check each option

   struct Person { var name: String } matches the correct syntax: struct Person { var name: String }. class Person { var name: String } uses class, not struct. struct Person = { var name: String } uses an invalid assignment syntax. struct Person: String { var name } incorrectly tries to inherit from String and misses type for name.

3. Final Answer:

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

4. Quick Check:

   Struct declaration uses struct Name { } [OK]

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

Common Mistakes:

• Using class keyword instead of struct
• Incorrect syntax with equals sign
• Missing type annotation for properties

3. Consider the following Swift code:

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

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

What will be printed?

medium

A. 1

B. 5

C. 0

D. Compilation error

Solution

1. Step 1: Understand struct copying behavior

   Since Point is a struct (value type), assigning p1 to p2 copies the data. They are independent.

2. Step 2: Analyze mutation and print

   Changing p2.x to 5 does not affect p1.x. So p1.x remains 1. The print statement outputs 1.

3. Final Answer:

   1 -> Option A

4. Quick Check:

   Structs copy on assignment, so original stays unchanged [OK]

Hint: Structs copy on assignment; changes don't affect original [OK]

Common Mistakes:

• Assuming p1.x changes when p2.x changes
• Confusing structs with classes (reference types)
• Expecting runtime error on mutation

4. The following Swift code tries to modify a property of a struct instance inside a function but causes a compile error:

struct Counter {
  var count: Int
}

func increment(counter: Counter) {
  counter.count += 1
}

What is the main reason for the error?

medium

A. Function parameter 'counter' is a constant by default

B. Struct properties cannot be modified inside functions

C. You cannot use '+=' operator on Int

D. Counter must be a class to modify properties

Solution

1. Step 1: Understand function parameter mutability

   In Swift, function parameters are constants by default. You cannot modify them inside the function.

2. Step 2: Analyze the error cause

   The parameter counter is a struct instance passed by value but immutable inside the function. Trying to change counter.count causes a compile error.

3. Final Answer:

   Function parameter 'counter' is a constant by default -> Option A

4. Quick Check:

   Function parameters are immutable unless marked inout [OK]

Hint: Function parameters are constants unless 'inout' is used [OK]

Common Mistakes:

• Thinking structs can't have mutable properties
• Believing '+=' is invalid for Int
• Assuming classes are required for mutation

5. You want to create a Swift type to represent a user profile that can be shared and updated across your app without copying. Which should you choose and why?

struct UserProfile {
  var name: String
  var age: Int
}

class UserProfileClass {
  var name: String
  var age: Int
  init(name: String, age: Int) {
    self.name = name
    self.age = age
  }
}

hard

A. Use struct because it copies data and prevents accidental changes.

B. Use class because structs cannot have properties.

C. Use class because it shares references and updates reflect everywhere.

D. Use struct because classes cannot have initializers.

Solution

1. Step 1: Identify sharing vs copying needs

   If you want updates to reflect everywhere (shared state), you need a reference type.

2. Step 2: Match type to behavior

   class is a reference type, so instances are shared. struct copies data, so changes won't reflect across copies.

3. Final Answer:

   Use class because it shares references and updates reflect everywhere. -> Option C

4. Quick Check:

   Shared mutable state = class [OK]

Hint: Choose class for shared mutable data, struct for copies [OK]

Common Mistakes:

• Choosing struct when shared updates are needed
• Thinking classes can't have initializers
• Believing structs can't have properties