Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The advice in the 2014 talk applies to exporting specific types of errors as part of a package’s public API surface.

The article, on the other hand, advocates for local variables storing errors not to have distinct names.



So a public variable error should follow different naming conventions then a local variable? That doesn't seem right, the go wiki says you should use the 'err' prefix for both (capitalized for public variables though, obviously)

And I'm only asking about when you are giving an error a distinct name, not just naming it 'err'.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: