News for hackers. Stuff that matters.
Re:I’m joining the Go team at Google by Conlectus on Friday September 23, 2016 @10:33AM (#12564896)
Any error return values in go must be assigned to a variable at call time, otherwise it's a compile error. Unused variables are also a compile error, so you are forced to do something with it.

Assigning to _ effectively ignores the error, but is considered a very bad practice.

Unavoidable runtime errors (eg divide by 0) will generate a panic, which is similar to an exception, but is uncatchable within the Go routine it originates in.

Re:I’m joining the Go team at Google by danieldk on Friday September 23, 2016 @10:40AM (#12564942)
Any error return values in go must be assigned to a variable at call time, otherwise it's a compile error.

Nonsense.

   fmt.Println("Hello world!")
I just ignored an error and it compiles fine. Go check the return type of Println:

https://golang.org/pkg/fmt/#Println

tl;dr, it's very easy to accidentally ignore errors in functions that are side-effecting or modify parameters. Been there, done that.

Re:I’m joining the Go team at Google by pmarreck on Friday September 23, 2016 @12:12PM (#12565668)
Yeah, that's what I thought. And I've also been there, done that. Is there basically some willful blindness around this issue with Go fans, or something? Or a lack of experience doing code? Or am I completely missing something?