My point is less about The Monad and more about being able to treat maybe-errors as a value.
Conversation
'try?' doesn't foreclose on the ability to capture a maybe-error into a value.
1
It increases the inertia of Optionalish errors rather than Eitherish errors (i.e., an afterthought).
2
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
Replying to
Unfortunately there is no unwasteful method of converting arbitrary async calls to sync calls on Apple’s platform.
Replying to
I think I'll make some speed tests and change it to the fastest
2
It’s not really about “fast” in terms of execution time: the issue is that blocking a system thread uses up kernel resources.
1
2
Show replies