News for hackers. Stuff that matters.
Re:On Scala by the1 on Wednesday June 19, 2013 @07:42AM (#5904938)
let's say you have more than one future:

    findAirline:        AirlineCode =>                Future[Option[Airline]]
    getFlightsForToday: Airline =>                    Future[Seq[Flight]]
    findAvailable:      Seq[Flight] => Constraints => Future[Option[Flight]
compose them so that I get:

    findFlight: AirlineCode => Constraints => Future[Flight]
I don't want `Future[Option[Flight]]` since Future has own error handling (using Try). No cheating by using scalaz monad transformer.
Re:On Scala by yummyfajitas on Wednesday June 19, 2013 @08:13AM (#5905044)

    def getOrThrow[T](x: Option[T]): T = x.getOrElse(throw new AirlineError)

    def findFlight(code: AirlineCode, constraints: Constraints) = for {
      airline <- findAirline(code).map(getOrThrow)
      flights <- getFlightsForToday(airline)
      available <- findAvailable(flights, constraints).map(getOrThrow)
    } yield (available)
No idea why you consider using scalaz to be cheating.
Re:On Scala by the1 on Wednesday June 19, 2013 @09:19AM (#5905345)
ah, getOrThrow! nice.
Re:On Scala by saryant on Wednesday June 19, 2013 @11:05AM (#5905937)
I'll readily admit that my Scala isn't 100% idiomatic, I'm still learning!