Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Yeah... so far my Go stuff has had exceptional reliability, I verified I handled all error known conditions with errcheck (https://github.com/kisielk/errcheck) and just generally took the slow and plodding approach of handling everything explicitly. My app handles hundreds of thousands of concurrent connections, each one often using and/or spawning 4 or more goroutines.


view as:

Thanks for the errcheck link, I will be using that. Would Go authors consider building that into the compiler? That would make quite a bit of sense.

As soon as I first used errcheck, I thought the exact same thing... "this should be included as warnings"

Legal | privacy