News for hackers. Stuff that matters.
Re:JEP draft: Exception handling in switch by bedobi on Friday April 19, 2024 @02:31PM (#40090401)
> Checked exceptions in java also have that property

No they don't. How many times have you seen code like

    try { //whatever } catch (Exception e) { //now we're catching ALL exceptions, yay }
or, worse

    try { //whatever } catch (Error e) { //lol }
re syntax, I guess some folks like more syntax but the point is if the syntax is being added to solve a problem that's solved in a way that's strictly objectively better in another way, it's pointless (and we're not talking about just complex syntax and all the foot guns and complexity that comes with hierarchies with exceptions, differences between checked and unchecked etc etc, we're talking about actual execution - try catch is at the end of the day a JVM hack that slows down execution and does something weird which could be easily avoided by just returning plain objects
Re:JEP draft: Exception handling in switch by shawnz on Friday April 19, 2024 @02:40PM (#40090503)
And in your scenario where you handle errors with an Either type, how many times have you seen code where that kind of thing just gets upcasted because the caller can't be bothered to deal with the specialized error? I think this is a strawman argument against exceptions and it's equally possible to do it wrong with your way as it is with my way.
Re:JEP draft: Exception handling in switch by vips7L on Friday April 19, 2024 @02:50PM (#40090636)
Rust:

   .unwrap() // error not possible
Kotlin:

   someNullValue!!.doIt() //can't be null here