"The import might fix the problem" 
This pull request by @odersky adds checked exceptions to Scala 3.
https://github.com/lampepfl/dotty/pull/11721 …pic.twitter.com/LkSB7xmu9S
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Well, considering Scala doesn't care too much about being "pure", that would be nice to have, right?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Weird, when I was working in Java you basically needed to change checked to unchecked to use streams and lambdas to do anything useful.
-
Luckily the effect polymorphism story can be much better in a capability-based system, like the one proposed above.
End of conversation
New conversation -
-
-
It’s going to be amazing what scala 3 will look like by 2030 when it is released!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I didn't think checked exceptions were well regarded. Wasn't there some quote about the Java ones being a failed experiment?
-
They weren't, but I think it was more the ergonomics of using them in Java, and the fact you couldn't escape them today gave them that reputation.
- Show replies
New conversation -
-
-
This Tweet is unavailable.
-
I can't imagine it's intended for 3.0, due to the nature of the RC process, though that doesn't apply to features behind flags.
End of conversation
-
-
-
In all honesty I don't hate it, but I wish he worked on something more pressing. Like giving us newtypes.
-
opaque types?
- 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.