What if your code could do the math for you automatically, every time you ask for a value?
Why Adding computed properties in Swift? - Purpose & Use Cases
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.
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.
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.
func area() -> Double {
return width * height
}
let rectArea = rect.area()var area: Double {
return width * height
}
let rectArea = rect.areaIt makes your code cleaner and safer by treating calculated values like regular properties that always reflect the current state.
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.
Computed properties calculate values on demand.
They keep data consistent without extra calls.
They simplify code and reduce errors.
Practice
Solution
Step 1: Understand property types in Swift
Stored properties hold data directly, while computed properties calculate values when accessed.Step 2: Identify computed property behavior
Computed properties useget(and optionallyset) to calculate values dynamically instead of storing them.Final Answer:
A property that calculates a value instead of storing it. -> Option AQuick Check:
Computed property = calculates value [OK]
- Confusing computed properties with stored properties
- Thinking computed properties always store data
- Assuming computed properties cannot have setters
area to a struct Square that returns side * side?Solution
Step 1: Recognize computed property syntax
Computed properties use curly braces with agetblock or implicit return inside braces.Step 2: Match syntax to the options
var area: Int { return side * side } usesvar 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.Final Answer:
var area: Int { return side * side } -> Option BQuick Check:
Computed property syntax = var name: Type { return value } [OK]
- Using '=' instead of braces for computed properties
- Defining computed property as a function
- Using 'let' instead of 'var' for computed properties
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)Solution
Step 1: Understand the computed property setter
Settingc.diameter = 20triggers thesetblock, which setsradius = newValue / 2. So radius becomes 20 / 2 = 10.Step 2: Print the updated radius
After setting diameter, printingc.radiusoutputs 10.0.Final Answer:
10.0 -> Option DQuick Check:
Setter updates radius to 10.0 [OK]
- Ignoring the setter and expecting radius unchanged
- Confusing diameter and radius values
- Assuming syntax error due to setter
struct Rectangle {
var width: Double
var height: Double
var area: Double {
get { width * height }
set { width = newValue / height }
}
}Solution
Step 1: Analyze the setter logic
The setter dividesnewValuebyheight. Ifheightis zero, this causes a runtime error (division by zero).Step 2: Check other options
Getter syntax is correct without parentheses. Computed properties can have setters. Variables can bevar. So only the setter can cause division by zero if height is zero.Final Answer:
Setter can cause division by zero if height is zero. -> Option CQuick Check:
Division by zero risk in setter = Setter can cause division by zero if height is zero. [OK]
- Thinking getter needs parentheses
- Believing computed properties can't have setters
- Assuming width and height must be constants
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
}Solution
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.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.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 AQuick 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]
- Omitting the setter for fullName
- Not splitting the input string correctly
- Using stored property instead of computed
Ready to prove it?
Pass the test and this pattern moves unknown
