Go Error Handling Sucks - golang-nuts

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Go Error Handling Sucks
Received-SPF: neutral (google.com: 209.85.214.169 is neither permitted nor denied by best guess record for domain of d...@cheney.net) client-ip=209.85.214.169;
MIME-Version: 1.0
In-Reply-To: <b114ff52-39fc-473f-afbc-3d94ce6fdc67@googlegroups.com>
References: <b114ff52-39fc-473f-afbc-3d94ce6fdc67@googlegroups.com>
Date: Tue, 25 Sep 2012 04:06:21 +1000
Message-ID: <CANp9fE__rD75En6cMafTp=BupAgc+xFAr9=qiCa6tBUpS7R...@mail.gmail.com>
Subject: Re: [go-nuts] Go Error Handling Sucks
From: Dave Cheney <d...@cheney.net>
To: knotwel...@gmail.com
Cc: golang-nuts@googlegroups.com
Content-Type: multipart/alternative; boundary=14dae93b595a6cb63d04ca7672f7

--14dae93b595a6cb63d04ca7672f7
Content-Type: text/plain; charset=ISO-8859-1

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-for-go/
>
>
> http://www.yosefk.com/blog/error-codes-vs-exceptions-critical-code-vs-typical-code.html
>
> 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.
>
>  --
>
>
>

--14dae93b595a6cb63d04ca7672f7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Hello,</p>
<p dir=3D"ltr">If we are trading links, allow me to quote myself.=A0 </p>
<p dir=3D"ltr"> <a href=3D"http://dave.cheney.net/2012/01/18/why-go-gets-ex=
ceptions-right">http://dave.cheney.net/2012/01/18/why-go-gets-exceptions-ri=
ght</a></p>
<p dir=3D"ltr">I hope you do not dismiss Go so quickly. If you spend some t=
ime using the language, rather than being lead around by the great unwashed=
 on reddit, you may have an opportunity to change your mind. </p>
<p dir=3D"ltr">Dave</p>
<div class=3D"gmail_quote">On 25 Sep 2012 03:59,  &lt;<a href=3D"mailto:kno=
twel...@gmail.com">knotwel...@gmail.com</a>&gt; wrote:<br type=3D"attributi=
on"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
<div><br></div><div>Its a shame that such a fantastic language is missing a=
 better way to deal with errors.=A0</div><div>Exceptions might not be perfe=
ct, but are damn better than checking each and every function call.</div>
<div><br></div><div>Or am I missing something?</div><div><br></div><div>I j=
ust read a pair of posts that expresses these ideas much better than what I=
 could here.</div><div><br></div><div><a href=3D"http://uberpython.wordpres=
s.com/2012/09/23/why-im-not-leaving-python-for-go/" target=3D"_blank">http:=
//uberpython.wordpress.com/2012/09/23/why-im-not-leaving-python-for-go/</a>=
<br>
</div><div><br></div><div><a href=3D"http://www.yosefk.com/blog/error-codes=
-vs-exceptions-critical-code-vs-typical-code.html" target=3D"_blank">http:/=
/www.yosefk.com/blog/error-codes-vs-exceptions-critical-code-vs-typical-cod=
e.html</a><br>
</div><div><br></div><div>As one of the comments I read said: 99% of the ti=
me 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 th=
e caller an error code or message, end of the story. =A0I don&#39;t want to=
 check every freaking single function invocation for errors.</div>
<div>Its a shame, I really wanted to use go.</div><div><br></div>

<p></p>

-- <br>
=A0<br>
=A0<br>
</blockquote></div>

--14dae93b595a6cb63d04ca7672f7--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
