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
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.
But then it comes down to a question of what that style should be. A lot of it is bikeshedding: A match or a fold will both work, and there are advantages to concision as well as explicitness. But consistency is also valuable, which I guess is where the pressure was coming from.
My whole point is that *someone* things it's wrong, and what I meant by subjective, opinionated complexity. Why should those two expressions be considered wrong by anyone at any time? It's an immature stance and a complete waste of time. It's also taxing on motivation & emotion.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
