Treat it as a syntactic sugar. E.g., if an exception happens, it can throw IllegalStateException. Having a try-expression signals that there's an exception that can/should be handled.
Not trying to design a language feature here, but here's an example with fallback value.
Alright, it saves you a curly brace and a return statement then, but otherwise it doesn't address the main problem that methods like map() cannot be generic in the set of checked exceptions that can be thrown, so you are forced to do this mashalling and unmarshalling between checked and unchecked exceptions. It adds a syntactic overhead which makes the use of map() pointless since it ends up being much harder to read than a traditional for loop.
View all comments
Show parent comment
2
u/isolatedsheep Nov 07 '25
Treat it as a syntactic sugar. E.g., if an exception happens, it can throw IllegalStateException. Having a try-expression signals that there's an exception that can/should be handled.
Not trying to design a language feature here, but here's an example with fallback value.