Autoclosures (@autoclosure) in Swift - Mini Project: Build & Apply

Using @autoclosure in Swift

📖 Scenario: Imagine you are building a simple logging system for an app. Sometimes, you want to log messages only if a certain condition is true. To make logging easier and efficient, you will use @autoclosure to delay the creation of log messages until they are really needed.

🎯 Goal: You will create a function that takes a condition and a message using @autoclosure. The message will only be created and printed if the condition is true. This helps avoid unnecessary work when logging is not needed.

📋 What You'll Learn

Create a Boolean variable called shouldLog with the value true.

Create a function called logMessage that takes a Bool parameter called condition and a @autoclosure parameter called message of type String.

Inside logMessage, print the message only if condition is true.

Call logMessage with shouldLog and a message string that says "This is a logged message.".

Print the message only if shouldLog is true.

💡 Why This Matters

🌍 Real World

Logging systems often need to avoid building complex messages unless logging is enabled. Using <code>@autoclosure</code> helps delay message creation until necessary.

💼 Career

Understanding <code>@autoclosure</code> is useful for Swift developers working on performance-sensitive apps, especially when implementing logging, assertions, or lazy evaluation.

1

Create the logging condition variable

Create a Boolean variable called shouldLog and set it to true.

Swift

# Your code here

Hint

Use var shouldLog = true to create the variable.

2

Define the logMessage function with @autoclosure

Create a function called logMessage that takes a Bool parameter named condition and a @autoclosure parameter named message of type String. Inside the function, print the message only if condition is true.

Swift

var shouldLog = true
# Your code here

Hint

Define the function with @autoclosure for the message parameter and call it with message() inside the if block.

3

Call logMessage with shouldLog and a message

Call the function logMessage with the variable shouldLog and the message string "This is a logged message.".

Swift

var shouldLog = true

func logMessage(condition: Bool, message: @autoclosure () -> String) {
    if condition {
        print(message())
    }
}

# Your code here

Hint

Call logMessage with condition: shouldLog and the message string.

4

Print the logged message only if shouldLog is true

Run the program and observe that the message This is a logged message. is printed only if shouldLog is true.

Swift

var shouldLog = true

func logMessage(condition: Bool, message: @autoclosure () -> String) {
    if condition {
        print(message())
    }
}

logMessage(condition: shouldLog, message: "This is a logged message.")

# Your code here

Hint

Run the program. The message should print because shouldLog is true.

Practice

1. What does the @autoclosure attribute do in Swift?

easy

A. Converts a closure into a normal function

B. Forces immediate execution of a closure parameter

C. Automatically wraps an expression into a closure to delay its execution

D. Prevents a closure from capturing variables

Solution

1. Step 1: Understand the purpose of @autoclosure

   @autoclosure automatically wraps an expression passed as an argument into a closure, delaying its execution until called.

2. Step 2: Compare with other options

   Options B, C, and D describe behaviors unrelated to @autoclosure's purpose.

3. Final Answer:

   Automatically wraps an expression into a closure to delay its execution -> Option C

4. Quick Check:

   @autoclosure delays execution = A [OK]

Hint: Autoclosure delays code execution by wrapping it automatically [OK]

Common Mistakes:

• Thinking @autoclosure runs code immediately
• Confusing @autoclosure with normal closures
• Assuming it changes closure syntax

2. Which of the following is the correct way to declare a function parameter using @autoclosure in Swift?

easy

A. func check(_ condition: @autoclosure () -> Bool) { }

B. func check(@autoclosure condition: Bool) { }

C. func check(condition: @autoclosure Bool) { }

D. func check(_ condition: Bool @autoclosure) { }

Solution

1. Step 1: Recall correct syntax for @autoclosure

   The correct syntax places @autoclosure before the closure type: @autoclosure () -> Bool.

2. Step 2: Analyze each option

   func check(_ condition: @autoclosure () -> Bool) { } matches the correct syntax. Options A, B, and C misuse the attribute placement or type declaration.

3. Final Answer:

   func check(_ condition: @autoclosure () -> Bool) { } -> Option A

4. Quick Check:

   @autoclosure syntax = func check(_ condition: @autoclosure () -> Bool) { } [OK]

Hint: Remember: @autoclosure before closure type () -> Type [OK]

Common Mistakes:

• Placing @autoclosure after the type
• Using @autoclosure on non-closure types
• Omitting the closure arrow syntax

3. What will be the output of the following Swift code?

func logIfTrue(_ predicate: @autoclosure () -> Bool) {
    if predicate() {
        print("True")
    } else {
        print("False")
    }
}

logIfTrue(3 > 5)

medium

A. True

B. Runtime crash

C. Compile-time error

D. False

Solution

1. Step 1: Understand the function behavior

   The function takes a condition as an autoclosure and calls it inside the if statement.

2. Step 2: Evaluate the passed expression

   The expression 3 > 5 is false, so predicate() returns false, triggering the else branch.

3. Final Answer:

   False -> Option D

4. Quick Check:

   3 > 5 is false, so output = False [OK]

Hint: Evaluate the expression inside autoclosure when called [OK]

Common Mistakes:

• Assuming autoclosure runs immediately before function call
• Confusing true/false logic
• Expecting compile errors due to autoclosure

4. Identify the error in this Swift function using @autoclosure:

func execute(_ action: @autoclosure () -> Void) {
    action
}

execute(print("Hello"))

medium

A. Missing parentheses to call the closure inside the function

B. Incorrect use of @autoclosure on a Void return type

C. Cannot pass print statement as autoclosure

D. Function parameter should not be marked @autoclosure

Solution

1. Step 1: Check how the closure is called inside the function

   The parameter action is a closure and must be called with parentheses: action().

2. Step 2: Identify the error

   The code uses action without parentheses, so the closure is not executed, causing no output.

3. Final Answer:

   Missing parentheses to call the closure inside the function -> Option A

4. Quick Check:

   Closure must be called with () = Missing parentheses to call the closure inside the function [OK]

Hint: Call autoclosure with () to execute it inside function [OK]

Common Mistakes:

• Forgetting to call the closure with parentheses
• Thinking @autoclosure forbids Void closures
• Assuming print can't be autoclosure

5. Consider this Swift code using @autoclosure to log messages only when needed:

func log(_ message: @autoclosure () -> String, onlyIf condition: Bool) {
    if condition {
        print(message())
    }
}

log("Debug info", onlyIf: false)

What is the main benefit of using @autoclosure here?

hard

A. The function runs faster because closures are always synchronous

B. The message string is constructed only if the condition is true, saving resources

C. The message is printed twice automatically

D. The condition parameter becomes optional

Solution

1. Step 1: Understand how @autoclosure delays evaluation

   The message string expression is wrapped in a closure and only evaluated when message() is called.

2. Step 2: Analyze the condition effect

   Since condition is false, message() is never called, so the string is not constructed, saving computation.

3. Final Answer:

   The message string is constructed only if the condition is true, saving resources -> Option B

4. Quick Check:

   @autoclosure delays message creation = The message string is constructed only if the condition is true, saving resources [OK]

Hint: Autoclosure delays expensive expressions until needed [OK]

Common Mistakes:

• Thinking message is always created regardless of condition
• Assuming autoclosure prints automatically
• Confusing condition with message parameter