The ability to abstract over 'throws' is admittedly weak. I hope we'll improve.
Conversation
Throwing closures are definitely still very awkward, esp w/ async.
3
relevant: My library to convert betw (a)sync functions /w errors
1
Isn't updated to beta 6 yet, but I'm making great use of throwing closures there
1
Using semaphores to covert async to sync like that will lead to excessive system threads.
3
2
This is exactly the track I went down, and exactly the bomb I discovered at the end.
1
2
3
You can possibly escape if you inject coroutines. But Swift doesn't have them.
1
1
Solutions to this problem are extant and old. Needs kernel support to do it right though.
2
You can get pretty far with compiler-support, if you don't need to async 'mmap'.
2
Replying to
I *do* need to async mmap. :) But yeah, sure, I’ll take compiler support. :D