Structured concurrency model in Swift - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the structured concurrency model in Swift?

It is a way to organize asynchronous tasks so they start and finish in a clear, predictable order, making code easier to read and bugs easier to avoid.

intermediate

How does Task groups help in structured concurrency?

Task groups let you create a group of related tasks that run concurrently, and you wait for all of them to finish before moving on, keeping tasks organized.

intermediate

What happens if a child task throws an error in structured concurrency?

The error is propagated to the parent task, which can handle it or cancel other child tasks, ensuring errors are managed safely and predictably.

beginner

Why is structured concurrency compared to a family tree?

Because tasks have a clear parent-child relationship, like family members, so when a parent finishes or cancels, all its children do too, keeping things tidy.

beginner

What Swift keyword is used to start a new asynchronous task in structured concurrency?

The async keyword marks functions that run asynchronously, and await is used to wait for their results.

In Swift's structured concurrency, what ensures that child tasks complete before the parent task finishes?

A Manual thread management

B Global dispatch queues

C Task groups

D Completion handlers

Task groups manage child tasks and wait for all to finish before the parent continues.

What keyword do you use to wait for an asynchronous function's result in Swift?

A await

B async

C defer

D wait

The 'await' keyword pauses execution until the async function returns.

If a child task throws an error, what happens in structured concurrency?

A The error is ignored

B The program crashes immediately

C The child task restarts automatically

D The parent task receives the error

Errors from child tasks propagate to the parent to handle them properly.

Which of these is NOT a benefit of structured concurrency?

A Manual thread locking

B Automatic error propagation

C Clear task lifecycle

D Simplified cancellation

Structured concurrency avoids manual thread locking by managing tasks automatically.

What does the 'async' keyword indicate in Swift functions?

A Function runs synchronously

B Function can be awaited and runs asynchronously

C Function is deprecated

D Function is private

'async' marks functions that run asynchronously and can be awaited.

Explain the main idea of the structured concurrency model and why it helps in writing asynchronous Swift code.

Think about how tasks are organized like a family tree.

Describe how task groups work in Swift's structured concurrency and their role in managing multiple asynchronous tasks.

Imagine a group of friends working together and waiting for everyone to finish before leaving.

Practice

1. What is the main purpose of structured concurrency in Swift?

easy

A. To group tasks so they run safely and complete before continuing

B. To allow tasks to run forever without waiting

C. To make tasks run only on the main thread

D. To avoid using async and await keywords

Solution

1. Step 1: Understand structured concurrency concept

   Structured concurrency groups related tasks so they run safely and finish before the program moves on.

2. Step 2: Compare options with concept

   Only To group tasks so they run safely and complete before continuing correctly describes grouping tasks to run safely and complete before continuing.

3. Final Answer:

   To group tasks so they run safely and complete before continuing -> Option A

4. Quick Check:

   Structured concurrency = safe grouped tasks [OK]

Hint: Structured concurrency means tasks finish before moving on [OK]

Common Mistakes:

• Thinking tasks run forever without waiting
• Believing tasks only run on main thread
• Confusing structured concurrency with avoiding async/await

2. Which of the following is the correct syntax to create a task group in Swift?

easy

A. withTaskGroup(of: Int.self) { group in ... }

B. asyncGroup { ... }

C. taskGroup.run { ... }

D. TaskGroup { await ... }

Solution

1. Step 1: Recall correct task group syntax

   Swift uses withTaskGroup(of: Type.self) { group in ... } to create a task group.

2. Step 2: Check options for exact syntax

   Only withTaskGroup(of: Int.self) { group in ... } matches the correct syntax; others are invalid or made-up.

3. Final Answer:

   withTaskGroup(of: Int.self) { group in ... } -> Option A

4. Quick Check:

   Task group syntax = withTaskGroup(of:) [OK]

Hint: Task groups start with withTaskGroup(of:) [OK]

Common Mistakes:

• Using TaskGroup without 'with'
• Trying taskGroup.run which doesn't exist
• Using asyncGroup which is not a Swift keyword

3. What will be the output of this Swift code using a task group?

func fetchValues() async -> [Int] {
  await withTaskGroup(of: Int.self) { group in
    group.addTask { 3 }
    group.addTask { 7 }
    group.addTask { 2 }

    var results = [Int]()
    for await value in group {
      results.append(value)
    }
    return results.sorted()
  }
}

Task {
  let values = await fetchValues()
  print(values)
}

medium

A. [3, 7, 2]

B. [2, 3, 7]

C. [7, 3, 2]

D. Compilation error

Solution

1. Step 1: Understand task group execution

   The tasks return 3, 7, and 2 asynchronously. The for-await loop collects them in any order.

2. Step 2: Analyze the return statement

   The results array is sorted before returning, so output is sorted ascending: [2, 3, 7].

3. Final Answer:

   [2, 3, 7] -> Option B

4. Quick Check:

   Sorted results = [2, 3, 7] [OK]

Hint: Remember results are sorted before printing [OK]

Common Mistakes:

• Assuming tasks run in order added
• Forgetting the sorting step
• Thinking code causes compile error

4. Identify the error in this Swift code using a task group:

func calculateSum() async -> Int {
  await withTaskGroup(of: Int.self) { group in
    group.addTask { 10 }
    group.addTask { 20 }
    var total = 0
    for value in group {
      total += value
    }
    return total
  }
}

medium

A. Return type should be Void

B. Cannot add tasks inside withTaskGroup

C. Missing 'await' before 'for' loop

D. Variable 'total' should be declared outside the group

Solution

1. Step 1: Check for correct async iteration

   When iterating over a task group, 'for await' must be used to await each task's result.

2. Step 2: Identify missing 'await'

   The code uses 'for value in group' instead of 'for await value in group', causing a syntax error.

3. Final Answer:

   Missing 'await' before 'for' loop -> Option C

4. Quick Check:

   Async iteration requires 'for await' [OK]

Hint: Use 'for await' to loop over task groups [OK]

Common Mistakes:

• Using 'for' instead of 'for await' on task groups
• Thinking tasks can't be added inside withTaskGroup
• Misunderstanding return type requirements

5. You want to fetch user data and user posts concurrently using structured concurrency. Which approach correctly uses a task group to run both tasks and combine their results?

hard

A. Use DispatchQueue.global().async to run tasks and wait with sleep()

B. Run tasks sequentially without a task group to avoid concurrency issues

C. Create two separate Task blocks and return results without waiting

D. Use withTaskGroup to add two tasks fetching data and posts, then await all and return combined tuple

Solution

1. Step 1: Understand concurrency for multiple async tasks

   Structured concurrency uses task groups to run multiple async tasks concurrently and wait for all to finish.

2. Step 2: Evaluate options for correct concurrency usage

   Use withTaskGroup to add two tasks fetching data and posts, then await all and return combined tuple correctly uses withTaskGroup to add tasks, await their completion, and combine results safely.

3. Final Answer:

   Use withTaskGroup to add two tasks fetching data and posts, then await all and return combined tuple -> Option D

4. Quick Check:

   Task groups run and wait for multiple tasks [OK]

Hint: Use withTaskGroup to run and wait multiple tasks [OK]

Common Mistakes:

• Running tasks sequentially losing concurrency benefits
• Using DispatchQueue with sleep instead of structured concurrency
• Not waiting for tasks to finish before returning