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
If Scala 3.1 adopts checked exceptions, I'm looking forward to the day when I can declare a library method as, def foo: Bar throws E without worrying whether my users care about exceptions or not. Right now I must return either `Bar` or `Try[Bar]` and make _someone_ compromise.
The way checked exceptions work means that users who _do_ care about exceptions will be forced to declare or handle them. But the users who don't... they get to call `foo` with zero ceremony, just as the could before. But the library designer doesn't have to decide.
And what if you want to write a "let-it-fail" prototype but might want to make it safe later? The best part is that most of the code wouldn't change: no need to switch to for-comprehension style. Either you wrap the expression in try/catch, or declare its return type as throwing.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
