@psnively Having iterated over 4-5 solutions I'd gladly see any new ones! /cc @rolandkuhn @seanparsons
-
-
Replying to @viktorklang
@viktorklang@psnively@rolandkuhn@seanparsons .. And store the EC as an implicit val of the class. No more explicit passing EC around.1 reply 0 retweets 0 likes -
Replying to @ryanlecompte
@ryanlecompte that’s a good way to use it; Future cannot make many assumptions about context itself /cc@viktorklang@psnively@seanparsons1 reply 0 retweets 0 likes -
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
@rolandkuhn An EC accidently added to scope via inheritence is the same thing as an EC implicit elsewhere.
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.