Try? for optional result in Swift - Step-by-Step Execution

Concept Flow - Try? for optional result

Call throwing function

↓

Try? catches error?

↓

Return value

↓

Use optional result

Try? calls a function that might throw an error. If no error, it returns the value wrapped as optional. If error, it returns nil.

Execution Sample

Swift

enum ParseError: Error {
  case invalidFormat
}

func parseInt(_ str: String) throws -> Int {
  if let num = Int(str) { return num }
  else { throw ParseError.invalidFormat }
}

let result = try? parseInt("123")

This code tries to convert a string to an integer. If it works, result is the number wrapped as optional. If it fails, result is nil.

Execution Table

Step	Action	Function Call Result	Try? Result	Notes
1	Call parseInt("123")	Returns 123	Optional(123)	String "123" converts successfully
2	Call parseInt("abc")	Throws error	nil	String "abc" cannot convert, error caught by try?
3	Use result from try?	N/A	Optional(123) or nil	Result is optional Int or nil if error

💡 Execution stops after try? returns optional value or nil depending on success or error

Variable Tracker

Variable	Start	After 1	After 2	Final
result	nil	Optional(123)	nil	Depends on input string

Key Moments - 2 Insights

Why does try? return nil instead of crashing when an error happens?

Because try? catches the error internally and converts it to nil, as shown in execution_table row 2.

What type is the result variable after using try??

It is an optional type wrapping the function's return type, shown as Optional(123) or nil in variable_tracker.

Visual Quiz - 3 Questions

Look at the execution_table, what does try? return when parseInt throws an error?

A The error is thrown up and crashes the program

B An optional wrapping the error

C nil

D A default value like 0

💡 Hint

See execution_table row 2 where try? result is nil when error occurs

At which step does try? return Optional(123)?

A Step 2

B Step 1

C Step 3

D Never

💡 Hint

Check execution_table row 1 where parseInt returns 123 and try? wraps it

If parseInt always succeeds, how does variable_tracker for result change?

A result becomes Optional with value every time

B result stays nil

C result becomes non-optional Int

D result becomes an error

💡 Hint

See variable_tracker showing result changes to Optional(123) after success

Concept Snapshot

try? calls a throwing function and returns an optional result.
If function succeeds, try? returns Optional(value).
If function throws error, try? returns nil.
Use try? to safely handle errors without do-catch.
Result type is always optional of function's return type.

Full Transcript

In Swift, try? is used to call a function that might throw an error. Instead of crashing or requiring a do-catch block, try? catches any error and returns nil. If the function succeeds, try? returns the value wrapped as an optional. For example, calling try? parseInt("123") returns Optional(123). Calling try? parseInt("abc") returns nil because the string cannot be converted. This lets you handle errors simply by checking if the result is nil or not. The variable holding the try? result is always an optional type. This visual trace shows each step: calling the function, catching errors, and returning optional values or nil. Remember, try? is a safe way to get optional results from throwing functions.

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