Why Try? for optional result in Swift? - Purpose & Use Cases

The Big Idea

What if you could try risky code without the headache of messy error checks?

The Scenario

Imagine you have a function that might fail, like reading a file or converting text to a number. Without a simple way to handle errors, you have to write lots of code to check if it worked or not.

The Problem

Manually checking for errors every time is slow and makes your code messy. It's easy to forget to handle some errors, which can cause your app to crash or behave unexpectedly.

The Solution

Using try? lets you run code that might fail and automatically get a simple optional result. If it works, you get the value; if it fails, you get nil. This keeps your code clean and safe without extra error handling.

Before vs After

✗ Before

do {
  let result = try someFunction()
  print(result)
} catch {
  print("Failed")
}

✓ After

if let result = try? someFunction() {
  print(result)
} else {
  print("Failed")
}

What It Enables

You can quickly and safely try risky operations and handle failures gracefully with minimal code.

Real Life Example

When loading user settings from a file, try? lets you attempt to read the file and get nil if it's missing or corrupted, so your app can use default settings instead.

Key Takeaways

Try? simplifies error handling by returning an optional result.

It reduces code clutter and prevents crashes from unhandled errors.

It's perfect for quick, safe attempts at operations that might fail.

Practice

1. What does try? do when used with a throwing function in Swift?

easy

A. It runs the function and returns an optional result, nil if an error occurs.

B. It forces the function to crash if an error is thrown.

C. It catches the error and prints it automatically.

D. It converts the error into a string message.

Solution

1. Step 1: Understand try? behavior

   The try? keyword runs a throwing function and converts its result into an optional value.

2. Step 2: What happens on error?

   If the function throws an error, try? returns nil instead of crashing or propagating the error.

3. Final Answer:

   It runs the function and returns an optional result, nil if an error occurs. -> Option A

4. Quick Check:

   try? returns optional or nil on error [OK]

Hint: try? returns nil on error instead of crashing [OK]

Common Mistakes:

• Thinking try? crashes on error
• Assuming try? prints error messages
• Believing try? converts errors to strings

2. Which of the following is the correct syntax to use try? with a throwing function named loadData()?

easy

A. let data = try loadData()

B. let data = try! loadData()

C. let data = try?loadData

D. let data = try? loadData()

Solution

1. Step 1: Identify correct try? syntax

   The correct syntax requires try? followed by the function call with parentheses.

2. Step 2: Check each option

   let data = try loadData() uses try without ?, which doesn't return optional. let data = try! loadData() uses try! which forces crash on error. let data = try?loadData misses parentheses after function name.

3. Final Answer:

   let data = try? loadData() -> Option D

4. Quick Check:

   try? requires parentheses for function call [OK]

Hint: Use try? followed by function call with parentheses [OK]

Common Mistakes:

• Omitting parentheses after function name
• Using try without ? for optional
• Using try! which forces crash on error

3. Consider this Swift code:

func fetchNumber() throws -> Int {
  if Bool.random() { return 10 } else { throw NSError() }
}

let result = try? fetchNumber()
print(result)

What are possible outputs?

medium

A. Prints either Optional(10) or nil

B. Always prints Optional(10)

C. Always prints nil

D. Causes a runtime crash

Solution

1. Step 1: Understand fetchNumber behavior

   The function randomly returns 10 or throws an error.

2. Step 2: Effect of try? on fetchNumber

   Using try? converts the throwing call into an optional Int. If no error, it returns Optional(10). If error, it returns nil.

3. Final Answer:

   Prints either Optional(10) or nil -> Option A

4. Quick Check:

   try? returns optional or nil based on error [OK]

Hint: try? returns optional value or nil on error [OK]

Common Mistakes:

• Assuming always returns value
• Assuming always returns nil
• Expecting a crash on error

4. Identify the error in this Swift code snippet:

func readFile() throws -> String {
  throw NSError()
}

let content = try readFile()
print(content)

medium

A. print(content) is invalid syntax

B. Function readFile() should not throw error

C. Missing try? to handle error as optional

D. No error, code runs fine

Solution

1. Step 1: Check error handling in calling code

   The function readFile() throws an error, but the call uses plain try without handling errors.

2. Step 2: Fix error handling with try?

   Using try? converts the throwing call into an optional, preventing runtime crash and handling error gracefully.

3. Final Answer:

   Missing try? to handle error as optional -> Option C

4. Quick Check:

   Use try? to avoid crash on throwing function [OK]

Hint: Use try? to safely call throwing functions without crash [OK]

Common Mistakes:

• Using try without catch or try?
• Assuming throwing function never throws
• Thinking print causes error

5. You want to call a throwing function parseData() that returns a dictionary, but you want to safely get an empty dictionary if it fails. Which code correctly uses try? to achieve this?

hard

A. let dict = try parseData() ?? [:]

B. let dict = try? parseData() ?? [:]

C. let dict = try! parseData() ?? [:]

D. let dict = parseData() ?? [:]

Solution

1. Step 1: Understand requirement for safe call

   You want to call a throwing function and get an optional result, defaulting to empty dictionary if it fails.

2. Step 2: Use try? with nil coalescing

   Using try? converts the throwing call to optional. The ?? [:] provides empty dictionary if nil.

3. Final Answer:

   let dict = try? parseData() ?? [:] -> Option B

4. Quick Check:

   try? with ?? gives safe default on error [OK]

Hint: Combine try? with ?? to provide default value [OK]

Common Mistakes:

• Using try without ? causes crash on error
• Using try! forces crash on error
• Calling throwing function without try