code review 824045: Language FAQ: update the entry on exceptions.

Language FAQ: update the entry on exceptions.

[r, 2010-04-07 22:46:50]

Hello golang-dev@googlegroups.com,

I'd like you to review this change.

[rsc, 2010-04-07 22:52:28]

I'm not sure the clumsy and awkward tags get quite
the meaning you want.  I think the important part about
Go's panic is that, as you've pointed out before,
it is deliberately linked with the containing function
being torn down.  Can we point at that as the way
to discourage overuse?

Russ

[adg1, 2010-04-07 22:55:58]

On 8 April 2010 08:52, Russ Cox <rsc@golang.org> wrote:
> I'm not sure the clumsy and awkward tags get quite
> the meaning you want.  I think the important part about
> Go's panic is that, as you've pointed out before,
> it is deliberately linked with the containing function
> being torn down.  Can we point at that as the way
> to discourage overuse?

Agree. Stating that we deliberately made features of the language
difficult to use (even with a sound rationale) is just asking for
trouble. A side-effect (not sure if it's worth mentioning) of linking
panic to the containing function is that it encourages you to write
simpler code where panic/recover are used.

[r2, 2010-04-07 22:56:14]

PTAL

[rsc1, 2010-04-07 23:00:09]

LGTM

[r, 2010-04-07 23:01:57]

Hello rsc (cc: golang-dev@googlegroups.com),

Please take another look.

[iant, 2010-04-07 23:02:33]

FYI

http://codereview.appspot.com/824045/diff/10001/11001
File doc/go_lang_faq.html (right):

http://codereview.appspot.com/824045/diff/10001/11001#newcode285
doc/go_lang_faq.html:285: We believe that coupling the usual idea of exceptions
to a control
I think you can omit "the usual idea of".

http://codereview.appspot.com/824045/diff/10001/11001#newcode289
doc/go_lang_faq.html:289: exceptional.  And then the type system gets mixed in.
I think I know what you mean by the type system comment, but, as you hint, it
seems orthogonal to rest of the paragraph.  I'm not sure it adds anything.

http://codereview.appspot.com/824045/diff/10001/11001#newcode292
doc/go_lang_faq.html:292: Go takes a different approach.  Instead of exceptions,
it has couple
s/has couple/has a couple/

http://codereview.appspot.com/824045/diff/10001/11001#newcode296
doc/go_lang_faq.html:296: to handle catastrophe but awkward enough to discourage
overuse.
Maybe s/awkward enough to discourage overuse/avoids conflating exceptions with a
control structure/

[r, 2010-04-07 23:03:17]

*** Submitted as http://code.google.com/p/go/source/detail?r=6236a8c15722 ***

Language FAQ: update the entry on exceptions.

R=rsc, iant
CC=golang-dev
http://codereview.appspot.com/824045