News for hackers. Stuff that matters.
Re:Sub-millisecond GC pauses in Go 1.8 by premium-concern on Saturday October 29, 2016 @02:00PM (#12825311)

  (value, no error)
  (value, error)
  (no value, error)
  (no value, no error)
Re:Sub-millisecond GC pauses in Go 1.8 by leaveyou on Saturday October 29, 2016 @03:22PM (#12825809)
The convention is that if the err == nil then the value is not nil. The exceptions to this rule are very few and usually specified in the documentation. Normally you only have to check for error.
Re:Sub-millisecond GC pauses in Go 1.8 by bluejekyll on Saturday October 29, 2016 @06:07PM (#12826687)
The fact that it's a convention, and not a compiler error is the entire issue at debate here.
Re:Sub-millisecond GC pauses in Go 1.8 by weberc2 on Saturday October 29, 2016 @04:20PM (#12826130)
There is no "no value" representation for int64. The only two cases are "<int64>, nil" or "<int64>, <error>".