You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Saddest to me is, I have worked on projects where if I don't use these obscure Scala expressions, my code won't pass reviews. This is my biggest turnoff to FP. It's infected w entirely subjective, opinionated complexity. As if any other kind of non-imparative expression is wrong.
I think that obscurity can be subjective too, though. I can't speak for your code reviews, but developers often extrapolate from their experience and try to overgeneralize it with what appears to be unwarranted conviction to anyone else. I think that's quite common in FP.
To be explicit, if I write the following, it is wrong, "not FP enough": val a = o match { case Some(x) => f(x); case None => y } I must refactor to this: val a = o.fold(y)(f) I've been told that if-else *expressions* and getOrElse() should be removed from lang/lib.
You mean *someone* thinks its wrong... But I think it's useful for projects to have a "house style". FP sometimes presents a few ways of doing the same thing, and it's easier for someone new to understand the code if everyone on the team uses the same style.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
