Introducing ClosureChains to avoid "completion hell"

[dannys42 (Danny Sung)]

ClosureChain helps to simplify sequential async calls by providing a familiar try-catch pattern for async methods. It's a library that makes no promises and has no future.

There's plenty of other more complicated solutions to this problem, but for those with simpler use-cases, I hope this helps.

[Cyberbeni (Benedek Kozma)]

I don't want to be the bringer of bad news but async/await is already available in preview and might make your project deprecated: swift-evolution/0296-async-await.md at main · apple/swift-evolution (github.com)

[Pitch #2] Async/await

What is the simplest asynchronous context where I can start playing with async/await? It depends on your definition of "playing with" :) If you're happy to write code against the model and see how it type-checks to get a feel for things, then grab a main snapshot from swift.org and go ahead. The type checker implementation (behind -Xfrontend -enable-experimental-concurrency) is very close to what's in the proposal, with a few stragglers for recent changes. If you want to actually execute s…

[dannys42 (Danny Sung)]

Thanks for the info. I'm aware of it, hence my cheeky slogan for "having no future". :-) But in all seriousness, as someone having to make do with the current versions of Swift, I needed something to make async a little more friendly, even if it's a relatively short-lived library.

FWIW, ClosureChains also imposes no additional threads/queues/coroutines/etc in order to accomplish its task... in case that's a benefit to anyone.