Composing property wrappers in Swift

Introduction

Composing property wrappers lets you combine multiple behaviors on one property easily. It helps keep code clean and reusable.

You want to add validation and logging to a property at the same time.

You need to apply caching and thread safety together on a variable.

You want to reuse common property behaviors in different parts of your app.

You want to separate concerns by stacking small wrappers instead of one big wrapper.

Syntax

Swift

@Wrapper2 @Wrapper1 var propertyName: Type

Property wrappers are applied from right to left, so @Wrapper1 wraps the property first, then @Wrapper2 wraps the result.

Each wrapper must have an initializer compatible with the wrapped property.

Examples

This property is first clamped between 0 and 10, then logged when changed.

Swift

@Logged @Clamped(min: 0, max: 10) var score: Int = 5

The name is trimmed of spaces and saved in user defaults.

Swift

@UserDefault("username") @Trimmed var name: String = ""

Sample Program

This program shows two property wrappers combined. The health property is clamped between 0 and 100, and changes are logged.

Swift

import Foundation

@propertyWrapper
struct Clamped {
    private var value: Int
    let min: Int
    let max: Int

    var wrappedValue: Int {
        get { value }
        set { value = Swift.min(Swift.max(newValue, min), max) }
    }

    init(wrappedValue: Int, min: Int, max: Int) {
        self.min = min
        self.max = max
        self.value = Swift.min(Swift.max(wrappedValue, min), max)
    }
}

@propertyWrapper
struct Logged {
    private var storage: Clamped

    var wrappedValue: Int {
        get { storage.wrappedValue }
        set {
            let oldValue = storage.wrappedValue
            storage.wrappedValue = newValue
            print("Changing value from \(oldValue) to \(storage.wrappedValue)")
        }
    }

    init(wrappedValue: Int) {
        self.storage = Clamped(wrappedValue: wrappedValue, min: 0, max: 100)
    }

    init(wrappedValue: Clamped) {
        self.storage = wrappedValue
    }
}

struct Player {
    @Logged @Clamped(min: 0, max: 100) var health: Int = 50
}

var player = Player()
player.health = 120
player.health = -10
player.health = 80

Important Notes

Order matters: the wrapper closest to the property applies first.

Each wrapper can add its own logic like validation, logging, or storage.

Composing wrappers keeps code modular and easier to maintain.

Summary

Composing property wrappers means stacking multiple wrappers on one property.

They apply behaviors in order, from right to left.

This technique helps add multiple features cleanly and reuse code.

Practice

1. What does it mean to compose property wrappers in Swift?

easy

A. Apply property wrappers only to functions

B. Use only one property wrapper per property

C. Create a new property wrapper by subclassing another

D. Stack multiple property wrappers on a single property to combine behaviors

Solution

1. Step 1: Understand property wrappers

   Property wrappers add behavior to properties in Swift.

2. Step 2: Define composition meaning

   Composing means stacking multiple wrappers on one property to combine their effects.

3. Final Answer:

   Stack multiple property wrappers on a single property to combine behaviors -> Option D

4. Quick Check:

   Composing = stacking wrappers [OK]

Hint: Remember: composing means stacking wrappers on one property [OK]

Common Mistakes:

• Thinking only one wrapper can be used per property
• Confusing subclassing with composing
• Applying wrappers to functions instead of properties

2. Which of the following is the correct syntax to compose two property wrappers @WrapperA and @WrapperB on a property var value: Int such that @WrapperA is applied first (innermost)?

easy

A. @WrapperB @WrapperA var value: Int

B. @WrapperA @WrapperB var value: Int

C. var @WrapperA @WrapperB value: Int

D. var value: Int @WrapperA @WrapperB

Solution

1. Step 1: Recall property wrapper order

   Property wrappers apply from right to left, so the rightmost is applied first.

2. Step 2: Check syntax order

   Correct syntax places wrappers before the property, so @WrapperB @WrapperA var value: Int applies @WrapperA first, then @WrapperB.

3. Final Answer:

   @WrapperB @WrapperA var value: Int -> Option A

4. Quick Check:

   Right to left wrapper order = @WrapperB @WrapperA var value: Int [OK]

Hint: Remember wrappers apply right to left, so last wrapper is closest to var [OK]

Common Mistakes:

• Placing wrappers after the variable name
• Reversing the order of wrappers
• Using wrappers inside the variable declaration

3. Given these property wrappers:

 @propertyWrapper
 struct WrapperA {
   var wrappedValue: Int
   init(wrappedValue: Int) { self.wrappedValue = wrappedValue + 1 }
 }

 @propertyWrapper
 struct WrapperB {
   var wrappedValue: Int
   init(wrappedValue: Int) { self.wrappedValue = wrappedValue * 2 }
 }

 struct Example {
   @WrapperA @WrapperB var value: Int = 3
 }

What is the value of Example().value?

medium

A. 7

B. 8

C. 6

D. 10

Solution

1. Step 1: Apply wrappers right to left

   First, @WrapperB applies: 3 * 2 = 6.

2. Step 2: Apply @WrapperA next

   Then @WrapperA adds 1: 6 + 1 = 7.

3. Final Answer:

   7 -> Option A

4. Quick Check:

   (3 * 2) + 1 = 7 [OK]

Hint: Apply wrappers from right to left to find final value [OK]

Common Mistakes:

• Applying wrappers left to right
• Forgetting to add 1 in WrapperA
• Multiplying after adding instead of before

4. Consider this code snippet:

 @propertyWrapper
 struct WrapperX {
   var wrappedValue: Int
   init(wrappedValue: Int) { self.wrappedValue = wrappedValue + 5 }
 }

 struct Test {
   @WrapperX @WrapperX var number: Int = 10
 }

What is the error in this code?

medium

A. Cannot apply the same property wrapper twice on one property

B. The property wrapper's init is called twice, causing unexpected behavior

C. No error; code compiles and runs correctly

D. The property wrapper must have a default initializer

Solution

1. Step 1: Check if multiple same wrappers allowed

   Swift allows stacking the same property wrapper multiple times.

2. Step 2: Analyze wrapper initialization

   Each wrapper adds 5, so first adds 5 to 10 = 15, second adds 5 to 15 = 20.

3. Final Answer:

   No error; code compiles and runs correctly -> Option C

4. Quick Check:

   Same wrapper stacking allowed = No error; code compiles and runs correctly [OK]

Hint: Same wrapper can be stacked; no syntax error [OK]

Common Mistakes:

• Assuming duplicate wrappers cause errors
• Expecting default initializer requirement
• Confusing runtime behavior with compile errors

5. You want to create a property that is both clamped between 0 and 100 and logged when changed. You have two property wrappers:

 @propertyWrapper
 struct Clamped {
   private var value: Int
   let range: ClosedRange<Int>
   var wrappedValue: Int {
     get { value }
     set { value = min(max(newValue, range.lowerBound), range.upperBound) }
   }
   init(wrappedValue: Int, _ range: ClosedRange<Int>) {
     self.range = range
     self.value = min(max(wrappedValue, range.lowerBound), range.upperBound)
   }
 }

 @propertyWrapper
 struct Logged {
   private var value: Int
   var wrappedValue: Int {
     get { value }
     set {
       print("Value changed to \(newValue)")
       value = newValue
     }
   }
   init(wrappedValue: Int) {
     self.value = wrappedValue
   }
 }

 struct Settings {
   @Logged @Clamped(0...100) var score: Int = 150
 }

What will be printed and what is the final value of Settings().score?

hard

A. Prints 'Value changed to 150', final value 150

B. Prints nothing, final value 100

C. Prints 'Value changed to 100', final value 100

D. Prints 'Value changed to 0', final value 0

Solution

1. Step 1: Apply wrappers right to left

   First, @Clamped(0...100) clamps 150 to 100 in init.

2. Step 2: Then @Logged receives 100

   @Logged init sets value=100 directly (no setter called, no print).

3. Final Answer:

   Prints nothing, final value 100 -> Option B

4. Quick Check:

   Clamp then direct init set = no print, value 100 [OK]

Hint: Initial values chain through inits right to left; no setter/print on init [OK]

Common Mistakes:

• Thinking log prints during initialization
• Thinking clamp applies after log
• Assuming propagation calls inner setters