Stop using, opt match { case Some(x) => f(x); case None => y } Stop using, http://opt.map (f).getOrElse(y) Use, opt.fold(y)(f) I feel like I'm very late to this party.
-
fold does not play nicely with type inference @ Some(1).fold(Nil)(_ :: Nil) found : List[Int] required: scala.collection.immutable.Nil.type val res0 = Some(1).fold(Nil)(_ :: Nil) ^
Well... if you do have a `Some`! But that would seem like a potential error anyway, and there would be an equivalent error in the `match` alternative.
-
-
what does Some have anything to do with it not lubbing the two alternative result types?
-
I mean, if you statically know it's a Some, you can statically .get it. Or am I missing something?
- Show replies
New conversation -
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.