News for hackers. Stuff that matters.
Re:Toward Go 1.3 by tptacek on Tuesday February 11, 2014 @01:59PM (#7219563)
You're not "throwing". You're "panicking".
Re:Toward Go 1.3 by ithkuil on Wednesday February 12, 2014 @03:02AM (#7223137)
Or raising? That's just terminology. The behaviors of c++/java/python exceptions and Go panics are similar regardless of the name the keyword has in those language:

The execution is suspended, the stack unwound until the first handler, the handler has access to a value that is "thrown". Stack information is preserved in order to print meaningful stack traces.

C++/java/python have syntax sugar that performs a pattern match on the thrown object to decide whether to handle it or bubble it up, while in Go you do it manually, but other that that I don't see much of a difference in the mechanics of them to justify being so pedantic about the naming of the action.