On a tax summary screen, changing the filter quickly makes several API requests finish almost at once. To make sure only the result for the last filter chosen ends up on screen, how would you manage the requests and the state changes?
Every time the filter changes, cancel the previous request's Task and tag the new request with a generation number, then right before putting the response into state, check that its number matches the current generation and drop stale responses. Change state in one place only, a @MainActor ViewModel.
ConcurrencyShort answerBasics
You're building an image pipeline: download, resize, then save to the disk cache, and…
#cancellation
ConcurrencyShort answerBasics
In Swift Concurrency, when you create a Task { }, when and where does that code run?
#cancellation
ConcurrencyMultiple choiceAdvanced
Which of the following statements about structured concurrency (async let, TaskGroup) are…
#cancellation
ConcurrencyMultiple choiceExpert
In this Swift Concurrency code, which statement about what actually happens right after…
#cancellation