Is our async/await dream becoming true?
This week, a pull request with the title
"Add an option to build the concurrency library for back deployment." got merged, which means we should look forward to the release notes of the next Xcode beta.
It's not confirmed to be actually true, but it seems that the development team is taking backward compatibility for the new concurrency changes seriously.
This week's article is all about dropping OS versions and adopting new APIs. The same question arrives when the new concurrency changes become available. Until now, it wasn't really a discussion whether we should implement it at WeTransfer, as the APIs were iOS 15+ only either way. However, it seems that we can decide whether or not we want to migrate our code to use async/await.
Obviously, it's not that simple to change and refactor everything in existing projects. For us, the minimum to do is making sure often-used frameworks like our Networking package adopt and provide async/await as an alternative to existing methods. This way, we can progressively use async/await in new classes and structs we're creating.
Let's hope together for a new beta making our dream actually come true.
Enjoy this week's SwiftLee Weekly!
