Twitter | Search | |
This is the legacy version of twitter.com. We will be shutting it down on 15 December 2020. Please switch to a supported browser or device. You can see a list of supported browsers in our Help Center.
Sebastian Markbåge
Not to be a downer but I can't get excited about async/await after seeing algebraic effects in OCaml. I feel like we're arguing over scraps.
Reply Retweet Like More
Bradley Farias 11 Aug 16
Replying to @sebmarkbage
after working with co-routines I have no desire for that kind of forking in impure/mutable environments
Reply Retweet Like
Sebastian Markbåge 11 Aug 16
Replying to @bradleymeck
How is async/await better?
Reply Retweet Like
Alexey Golev 11 Aug 16
Replying to @sebmarkbage
try..catch for error handling is the reason I can’t see myself using async/await. And algebraic effects…I wish)
Reply Retweet Like
Evan Jacobs 15 Aug 16
writing try/catches always makes me feel dirty and inadequate
Reply Retweet Like
_darkfadr 11 Aug 16
Replying to @sebmarkbage
I just started using it and I really like it, definitely helps with readability
Reply Retweet Like
Sam Goldman 11 Aug 16
Replying to @sebmarkbage
effects, multicore, implicits—ocaml is getting more attractive by the day
Reply Retweet Like
Gorgi Kosev 11 Aug 16
multicore? where?
Reply Retweet Like
Joe Savona 11 Aug 16
Replying to @sebmarkbage
couldn't agree more.
Reply Retweet Like
Julien Goux 11 Aug 16
Replying to @sebmarkbage
This is why I favor fantasy-land's Future over async/await. At least it's truly monadic.
Reply Retweet Like
Gregor Müllegger 12 Aug 16
Replying to @sebmarkbage
is there a good introduction to algebraic effects and why they are so cool you can recommend?
Reply Retweet Like