News for hackers. Stuff that matters.
Re:Go 1.1 beta 1 Released by EdiX on Thursday April 04, 2013 @06:32AM (#5491857)
> Lack of exception handling is the biggest reason I haven't used Go for much.

Go does exception handling with panic, recover and its reflection syntax.

Re:Go 1.1 beta 1 Released by NateDad on Thursday April 04, 2013 @08:32AM (#5492207)
Using panic and recover is strongly discouraged, and in the rare cases where it makes the code significantly simpler, panics should never cross package boundaries (which is to say, you should never have a public API that can panic, unless you fully expect the panic to take down the process).
Re:Go 1.1 beta 1 Released by EdiX on Thursday April 04, 2013 @11:12AM (#5493103)
Using panics for control flow or having panics cross library boundaries is strongly discouraged, otherwise they are fine. Go's own standard library uses them internally in several places.

Even then discouraging panics is very different from not having them.

Re:Go 1.1 beta 1 Released by trailfox on Thursday April 04, 2013 @06:45AM (#5491887)
So if I'm reading from a file I should use panic recover and not return code checking?? That's not what I've seen in the docs.
Re:Go 1.1 beta 1 Released by jlgreco on Friday April 05, 2013 @12:02AM (#5496714)
You seem to be missing the difference between "can you do it" and "should you do it". The reason that you should not is because doing so is not idiomatic Go. You are completely able to do so though.