On Saturday, July 6, 2019 at 12:22:33 AM UTC+2, Jakub Labath wrote:
>
> Some of us had to fix so much broken java/python code with invisible and
> anonymous goto statements (aka exceptions) that even just seeing the
> keyword try prompts a physical reaction.
>
"Just seeing the keyword try prompts a physical reaction"?… Maybe this is
the issue with this discussion: too much emotions, not enough rational
arguments.
try is just syntactic sugar for `if err != nil { return ..., err }` and
nothing more.
try doesn't change the language grammar and semantics at all:
- error handling is still explicit;
- error are still values;
- there is still no stack unwinding;
- etc.
The comparison with exceptions (and anonymous goto statements) is
completely uncalled for.
I'm baffled by the amount of negative emotions, strong feelings and harsh
reactions to the addition of a minor built-in function whose sole goal is
to reduce verbosity by factoring out a repetitive pattern.
I'm seeing people lecturing the Go team about the "language philosophy" and
submitting "alternative proposals" without understanding the difference
between a keyword, a built-in function and a statement…
Maybe the try proposal is not perfect and maybe it needs to be improved.
It's open to discussion. The Go team has made it clear they will listen, as
they already did in the past with the check/handle proposal. But instead of
bringing constructive arguments to improve the proposal, many comments are
about killing the proposal, "leave if != err alone", and change nothing.
These comments summon the "community", but I'm afraid it's not the kind of
community I want to be in.
I have an immense respect for the design documents produced by the Go team
these last few years on many subjects: garbage collection, dependency
management, error handling, generics, etc. This is exactly the kind of
engineering I want to see and that made me use Go.
So please fellow gophers, continue to tell the Go team what you'd want to
be improved in the try proposal, but have a little faith in their work :-)
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/e337d6d6-3e73-4132-9776-11c904fabe5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
