It increases the inertia of Optionalish errors rather than Eitherish errors (i.e., an afterthought).
Conversation
I want the bad path to receive as much compositional power and valueness as the good path.
3
3
The ability to abstract over 'throws' is admittedly weak. I hope we'll improve.
3
7
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
Thanks for the feedback! Do you think dispatch_group would be better?
1
Unfortunately there is no unwasteful method of converting arbitrary async calls to sync calls on Apple’s platform.
1
I think I'll make some speed tests and change it to the fastest
2
Replying to
It’s just not something anyone should do in production. In a playground—sure.
Replying to
Yeah I know, the disclaimer in the beginning should prevent bad usage (I hope)