This is why #scalaz Futures are better than #scala Futures http://bit.ly/1pKUOJL
-
-
Replying to @etorreborre
@etorreborre that explains how#scala Futures behave. What is the difference with#scalaz Futures?4 replies 0 retweets 0 likes -
-
Replying to @dibblego
@dibblego@etorreborre thanks. That’s really helpful.1 reply 0 retweets 0 likes -
Replying to @dclinton
@dclinton@etorreborre They preserve equational reasoning, as shown. Consequently, they work.1 reply 4 retweets 1 like -
Replying to @dibblego
@dibblego@etorreborre those are useless answers to a practical question.@dclinton see http://docs.typelevel.org/api/scalaz/nightly/index.html#scalaz.concurrent.Future … for actual understanding4 replies 0 retweets 0 likes -
Replying to @jeanhelou
@jeanhelou@etorreborre@dclinton er no it is a precise answer to a direct question. Please come to know this.2 replies 0 retweets 0 likes -
Replying to @dibblego
@dibblego@jeanhelou@etorreborre precise, but unhelpful, as I do not feel at all helped by it. I’m sure you’ll blame me for that, tho.3 replies 0 retweets 0 likes -
Replying to @dclinton
@dclinton@dibblego@etorreborre in the case of the original article both code samples would then have the same behaviour2 replies 0 retweets 0 likes
@jeanhelou @dclinton @etorreborre Please take me off your shitty advice list now. Thanks.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.