Applicative for scalaz.concurrent.Task that 'automatically' parallelizes the applicative operations:https://gist.github.com/pchiusano/8965595 …
-
-
Replying to @jdegoes
@jdegoes@djspiewak@milessabin Yep. And even in Scala, it can be hard to *see* under import x.y._2 replies 0 retweets 0 likes -
Replying to @nuttycom
@nuttycom@jdegoes@djspiewak@milessabin Some languages get it right, where multiple type-class instances for a single type is absurd.1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@nuttycom@jdegoes@milessabin So…which Monoid[Boolean] instance do *you* like best? ^_^1 reply 0 retweets 0 likes -
Replying to @djspiewak
@djspiewak@nuttycom@jdegoes@milessabin No, that is not a solid argument.2 replies 0 retweets 0 likes -
Replying to @dibblego
@dibblego@nuttycom@jdegoes@milessabin It points out the arbitrary nature of the single-typeclass constraint though.1 reply 0 retweets 0 likes -
Replying to @djspiewak
@djspiewak@nuttycom@jdegoes@milessabin No, it really doesn't. This point looks at the surface through a spy-glass.1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@nuttycom@jdegoes@milessabin Obviously I’m snagging a specific case (and a rather useless one), but it’s an example.1 reply 0 retweets 0 likes -
Replying to @djspiewak
@djspiewak@nuttycom@jdegoes@milessabin Yes, let's list them all, then look at how criminal it is to suggest multiple instances for a type1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego would you be happier with locally indexed type classes than with local type classes? /cc@djspiewak@nuttycom@jdegoes1 reply 0 retweets 0 likes
@milessabin @djspiewak @nuttycom @jdegoes Yes actually, I would.
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.