Re: Filter on future doesn't make sense
Viktor Klang <[email protected]> Fri, 1 Jul 2016 09:06:39 +0200
| Newsgroups | gmane.comp.lang.scala |
|---|---|
| Message-ID | <CANPzfU9SiPp_MXJU1Hi43BViGW2v5QCJo6JPRLatr6d7_jD9vw@mail.gmail.com> |
Hi Avi, Use Fututre[Option[Int]] if you want to deal with Some/None as a result of filter ( f.map(_.filter(p) ) (alt. see monad transformers) -- Cheers, √ On Jul 1, 2016 8:53 AM, "Avi Levi" <[email protected]> wrote: I was trying to figure out what should I accept when filtering over a future . the current implementation yields either a T or an exception which kind of breaks referential transparency (doesn't it ?) . on the other hand what can I expect given this expression *def foo(i:Int):Future[Int]* the type result of *foo(1).filter(_ % 2 == 0)* I.M.H.O I would expect it to yield Option[T] which makes more sense to express that we might get a value that pass the filter or not . is that make sense ? Cheers Avi -- You received this message because you are subscribed to the Google Groups "scala-language" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "scala-language" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.