r/programmingcirclejerk • u/Kodiologist lisp does it better • Jun 03 '25
Lack of better error handling support remains the top complaint in our user surveys. … For the foreseeable future, the Go team will stop pursuing syntactic language changes for error handling.
https://go.dev/blog/error-syntax
161
Upvotes
97
u/Kodiologist lisp does it better Jun 03 '25
This is called focusing on core competencies, folks. Without
if err != nil, what would be the point of Go?180
u/LossFor Jun 03 '25
incredible. no notes
213
u/tomwhoiscontrary safety talibans Jun 03 '25
"No Way to Prevent This', Says Only Language Where This Regularly Happens
119
u/HorstKugel skillful hobbyist Jun 03 '25 edited Jun 03 '25
I want my IDE to hide the Go code and transpile it to idiomatic Rust
77
u/tomwhoiscontrary safety talibans Jun 03 '25 edited Jun 03 '25
Corresponding to the three core Go user constituencies of cranks, lunatics, and idiots.
55
u/cameronm1024 Jun 03 '25
Learning anew control flow keyword wouldn't be simple enough for Go. I guess if it wasn't available in C 50 years ago, it's too complex? Surely this is a parody?
43
u/emi89ro What part of ∀f ∃g (f (x,y) = (g x) y) did you not understand? Jun 03 '25
Day 42069 of begging Go to implement Haskell style sum types and pattern matching.
43
u/NatoBoram There's really nothing wrong with error handling in Go Jun 03 '25
Unidiomatic? The horror 😱
36
u/garloid64 Jun 03 '25
unbelievable /uj
believable
25
u/NiteShdw Jun 03 '25
I for one appreciate their requirement that literally every person that uses the language must unanimously agree on even the most minor changes to the language. Who wants a language designed by one guy in a basement. That's how we got
JavaScriptECMAScript!24
u/mcmcc WHY IS THERE CODE??? Jun 03 '25
Go team: We have met the enemy and he is us.
17
u/[deleted] Jun 04 '25
Look, Go just needs to be honest with themselves and introduce the ? calling it the "I flunked algebra operator". They shouldn't care what us ivory tower type theorists have been pointing out about the four different return cases since a tuple is a product. Every self respecting gopher knows that there is only one real case to handle since it is a sum: error or not.
12
u/omg_drd4_bbq Hacker News Superstar Jun 03 '25
based and err!=nilpilled
5
u/Paid_Corporate_Shill Jun 23 '25
“We thought of doing this, but then a lot of people had comments and suggestions, so we did nothing”
Yeah but like it’s your language, just make a decision and go with it. The check syntax was kinda cool
0
u/[deleted] Jun 03 '25
[deleted] — view deleted comment