Bird
Raised Fist0
Swiftprogramming~3 mins

Why Adding computed properties in Swift? - Purpose & Use Cases

Choose your learning style10 modes available
The Big Idea

What if your code could do the math for you automatically, every time you ask for a value?

The Scenario

Imagine you have a class representing a rectangle, and you want to get its area. Without computed properties, you might have to write a separate function or manually calculate the area every time you need it.

The Problem

This manual approach means you have to remember to call the function each time, risking mistakes or forgetting to update the area if the rectangle changes. It's repetitive and error-prone.

The Solution

Adding computed properties lets you define a property that automatically calculates its value when accessed. This means you can get the area just like any other property, and it always stays up-to-date without extra effort.

Before vs After
✗ Before
func area() -> Double {
    return width * height
}
let rectArea = rect.area()
✓ After
var area: Double {
    return width * height
}
let rectArea = rect.area
What It Enables

It makes your code cleaner and safer by treating calculated values like regular properties that always reflect the current state.

Real Life Example

Think of a shopping cart app where the total price updates automatically as you add or remove items, without needing to call a separate update function.

Key Takeaways

Computed properties calculate values on demand.

They keep data consistent without extra calls.

They simplify code and reduce errors.

Practice

(1/5)
1. What is a computed property in Swift?
easy
A. A property that calculates a value instead of storing it.
B. A property that stores a fixed value only.
C. A property that can only be set once.
D. A property that is always optional.

Solution

  1. Step 1: Understand property types in Swift

    Stored properties hold data directly, while computed properties calculate values when accessed.
  2. Step 2: Identify computed property behavior

    Computed properties use get (and optionally set) to calculate values dynamically instead of storing them.
  3. Final Answer:

    A property that calculates a value instead of storing it. -> Option A
  4. Quick Check:

    Computed property = calculates value [OK]
Hint: Computed properties calculate values on demand, not store them [OK]
Common Mistakes:
  • Confusing computed properties with stored properties
  • Thinking computed properties always store data
  • Assuming computed properties cannot have setters
2. Which of the following is the correct syntax to add a computed property area to a struct Square that returns side * side?
easy
A. func area() -> Int { side * side }
B. var area: Int { return side * side }
C. var area: Int = side * side
D. let area = side * side

Solution

  1. Step 1: Recognize computed property syntax

    Computed properties use curly braces with a get block or implicit return inside braces.
  2. Step 2: Match syntax to the options

    var area: Int { return side * side } uses var area: Int { return side * side }, which is correct for a computed property. var area: Int = side * side tries to assign directly, which is invalid for computed properties.
  3. Final Answer:

    var area: Int { return side * side } -> Option B
  4. Quick Check:

    Computed property syntax = var name: Type { return value } [OK]
Hint: Use braces and return for computed properties, not direct assignment [OK]
Common Mistakes:
  • Using '=' instead of braces for computed properties
  • Defining computed property as a function
  • Using 'let' instead of 'var' for computed properties
3. What will be the output of this Swift code?
struct Circle {
    var radius: Double
    var diameter: Double {
        get { radius * 2 }
        set { radius = newValue / 2 }
    }
}

var c = Circle(radius: 5)
c.diameter = 20
print(c.radius)
medium
A. 5.0
B. Syntax error
C. 20.0
D. 10.0

Solution

  1. Step 1: Understand the computed property setter

    Setting c.diameter = 20 triggers the set block, which sets radius = newValue / 2. So radius becomes 20 / 2 = 10.
  2. Step 2: Print the updated radius

    After setting diameter, printing c.radius outputs 10.0.
  3. Final Answer:

    10.0 -> Option D
  4. Quick Check:

    Setter updates radius to 10.0 [OK]
Hint: Setter changes radius to half the diameter value [OK]
Common Mistakes:
  • Ignoring the setter and expecting radius unchanged
  • Confusing diameter and radius values
  • Assuming syntax error due to setter
4. Identify the error in this computed property code:
struct Rectangle {
    var width: Double
    var height: Double
    var area: Double {
        get { width * height }
        set { width = newValue / height }
    }
}
medium
A. width and height must be constants (let).
B. Getter must have parentheses after width * height.
C. Setter can cause division by zero if height is zero.
D. Computed properties cannot have setters.

Solution

  1. Step 1: Analyze the setter logic

    The setter divides newValue by height. If height is zero, this causes a runtime error (division by zero).
  2. Step 2: Check other options

    Getter syntax is correct without parentheses. Computed properties can have setters. Variables can be var. So only the setter can cause division by zero if height is zero.
  3. Final Answer:

    Setter can cause division by zero if height is zero. -> Option C
  4. Quick Check:

    Division by zero risk in setter = Setter can cause division by zero if height is zero. [OK]
Hint: Check for zero in divisor inside setter to avoid runtime errors [OK]
Common Mistakes:
  • Thinking getter needs parentheses
  • Believing computed properties can't have setters
  • Assuming width and height must be constants
5. You want to add a computed property fullName to this struct that combines firstName and lastName with a space, and also allows setting both names by splitting the input string. Which code correctly implements this?
struct Person {
    var firstName: String
    var lastName: String
    // Add fullName computed property here
}
hard
A. var fullName: String { get { "\(firstName) \(lastName)" } set { let parts = newValue.split(separator: " ") if parts.count == 2 { firstName = String(parts[0]) lastName = String(parts[1]) } } }
B. var fullName: String { return "\(firstName) \(lastName)" }
C. var fullName: String { get { firstName + lastName } set { firstName = newValue } }
D. var fullName: String = ""

Solution

  1. Step 1: Understand the requirements

    The computed property must combine first and last names with a space in the getter, and split the input string to set both names in the setter.
  2. Step 2: Evaluate each option

    var fullName: String { get { "\(firstName) \(lastName)" } set { let parts = newValue.split(separator: " ") if parts.count == 2 { firstName = String(parts[0]) lastName = String(parts[1]) } } } correctly implements a getter returning "firstName lastName" and a setter splitting the input string into two parts to assign firstName and lastName. var fullName: String { return "\(firstName) \(lastName)" } lacks a setter. var fullName: String { get { firstName + lastName } set { firstName = newValue } } concatenates without space and sets only firstName. var fullName: String = "" is a stored property, not computed.
  3. Final Answer:

    var fullName: String { get { "\(firstName) \(lastName)" } set { let parts = newValue.split(separator: " ") if parts.count == 2 { firstName = String(parts[0]) lastName = String(parts[1]) } } } -> Option A
  4. Quick Check:

    Computed property with get and set splitting string = var fullName: String { get { "\(firstName) \(lastName)" } set { let parts = newValue.split(separator: " ") if parts.count == 2 { firstName = String(parts[0]) lastName = String(parts[1]) } } } [OK]
Hint: Use get for combining and set for splitting names [OK]
Common Mistakes:
  • Omitting the setter for fullName
  • Not splitting the input string correctly
  • Using stored property instead of computed
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard