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.
interesting take, contrary to many opinions I've heard. Thanks for making it
I'd guess the other opinions are based on experience with checked exceptions in other languages, which Scala 3's approach acknowledges wholeheartedly, and attempts to fix. Or, I might speculate, from an overattachment to a monadic style... ;)
Didn't you have a library for letting users choose?
When I saw him present it, I thought it was one of the coolest things ever
One place when I will absolutely appreciate checked exceptions in Scala is interaction with Java libraries.
I have mixed feelings about this capability. Most of the time when something fails in a system, I just want to know if it's retryable or not. Having a complex exception domain has never really helped in my experience.
Wasn't this checked exception thing meant as a first test balloon for some kind of language-integrated effect system?
Yes, but that's maybe underselling it... it has a variety of other possibilities, though this one seems like the most tangible one to me.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
