@ryanlecompte that’s a good way to use it; Future cannot make many assumptions about context itself /cc @viktorklang @psnively @seanparsons
-
-
Replying to @rolandkuhn
@rolandkuhn@ryanlecompte@viktorklang@psnively The Scalaz Future looks like it solves the problem as I have it with ReaderT.2 replies 0 retweets 0 likes -
Replying to @seanparsons
@seanparsons@rolandkuhn@ryanlecompte@viktorklang@psnively You can trap an ExecutionContext in an instance of Monad[Future] (akka).1 reply 0 retweets 0 likes -
Replying to @rolandkuhn
@rolandkuhn Also, we found that tons of implicit execution contexts lead to some things being run in the wrong threadpool :\2 replies 0 retweets 0 likes -
Replying to @tixxit
@tixxit@rolandkuhn And M[+_]: Monad on a method is not the same as another M[+_]: Monad in a higher scope, so types help. ECs are ECs.2 replies 0 retweets 0 likes -
Replying to @rolandkuhn
@rolandkuhn Yeah, there are definitely multiple ways to skin a cat, and type tagging, wrapping ,etc is nice. We abstract over our monads:)1 reply 0 retweets 0 likes -
Replying to @tixxit
@tixxit@rolandkuhn Truthfully, not much our code runs in a bare Future, but often a monad transformer w/ Future.1 reply 0 retweets 0 likes
@rolandkuhn Definitely. I may not have replied similarily (/at all) if it wasn't @seanparsons
-
-
Replying to @tixxit
@tixxit@rolandkuhn Sounds like I should be proud of that! :)0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.