News for hackers. Stuff that matters.
Re:Why Go Is Not Good by rakoo on Sunday June 29, 2014 @05:46PM (#7962572)
> It's a common pattern in lazy construction to check if the receiving pointer is nil before continuing.

I disagree: if the construction can fail, the constructor must return an error, which will be checked; only if the error is nil can the process continue. There shouldn't be logic on the actual data returned to assert whether a constructor worked or not.

Re:Why Go Is Not Good by tshadwell on Sunday June 29, 2014 @05:54PM (#7962607)
I meant something like this:

http://play.golang.org/p/eqnDLVMHGA (pseudocode)