Asynchronous programming and concurrency are key when building responsive and fluid end user experiences for mobile apps. Numerous tools and techniques are available to deal with asynchronous and concurrent programming.
Swift 5.5 introduces a new set of features for this purpose, most notably the async/await pattern and actors. This has long been awaited by developers and will most likely become the primary way to write asynchronous code on Apple's platforms going forward. But does it live up to its promise of safe structured concurrency? How does it compare to other existing solutions?
Extract and rewrite an existing concurrent implementation to an implementation that makes use of Swift's new concurrency model. Analyze performance differences for different scenarios, both in terms of speed as well as of memory consumption.