News for hackers. Stuff that matters.
Re:The Reliability of Go by jussij on Sunday October 20, 2013 @07:44PM (#6582116)
As I don't program in Go this might be wrong, but doesn't the programmer have to tell the Go compiler to ignore the error by using the _ variable thing?

In that sense Go is still forcing the programmer to handle the error and it is the programmer who is deciding to ignore it.

I can see making the programmer do nothing more than mark the error as ignored still forces the programmer to think about the error and as such adds some value.

Re:The Reliability of Go by AYBABTME on Sunday October 20, 2013 @08:51PM (#6582400)
Unless you ignore all returned values:

   func Something() (a, bunch, of, stuff) {
      // stuff
   }

   ...
   _, _, _, _ = Something()
   Something()
Both are valid.
Re:The Reliability of Go by jussij on Monday October 21, 2013 @01:53AM (#6583610)
Thanks for that.

I would have though that in a language all about error checking this would not be allowed:

    Something()
But there you go, I've learnt something new about Go.
Re:The Reliability of Go by masklinn on Monday October 21, 2013 @04:02AM (#6584039)
> in a language all about error checking

Go is not one such language, that's one of the numerous go myths completely disconnected from reality.