Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
golang-nuts
Home
+ new post
About this group
Join this group
Message from discussion Go Error Handling Sucks
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Dave Cheney  
View profile  
 More options Sep 24 2012, 2:06 pm
From: Dave Cheney <d...@cheney.net>
Date: Tue, 25 Sep 2012 04:06:21 +1000
Local: Mon, Sep 24 2012 2:06 pm
Subject: Re: [go-nuts] Go Error Handling Sucks
Print | View thread | Show original | Report this message | Find messages by this author

Hello,

If we are trading links, allow me to quote myself.

http://dave.cheney.net/2012/01/18/why-go-gets-exceptions-right

I hope you do not dismiss Go so quickly. If you spend some time using the
language, rather than being lead around by the great unwashed on reddit,
you may have an opportunity to change your mind.

Dave
On 25 Sep 2012 03:59, <knotwel...@gmail.com> wrote:

> Its a shame that such a fantastic language is missing a better way to deal
> with errors.
> Exceptions might not be perfect, but are damn better than checking each
> and every function call.

> Or am I missing something?

> I just read a pair of posts that expresses these ideas much better than
> what I could here.

> http://uberpython.wordpress.com/2012/09/23/why-im-not-leaving-python-...

> http://www.yosefk.com/blog/error-codes-vs-exceptions-critical-code-vs...

> As one of the comments I read said: 99% of the time I need to code the
> happy path and if something breaks in the middle the error handling is
> exactly the same: log the error, close resources, send the caller an error
> code or message, end of the story.  I don't want to check every freaking
> single function invocation for errors.
> Its a shame, I really wanted to use go.

>  --


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google