and change existing
> code, but it is just busy work. The Go error handling is worse than C in
> that at least in C, the api doc clearly spells out which error codes can be
> returned, and why. With the Go error interface, and the 'minimal api doc',
> what is returned when
Number 4,5,6 on the list all are listed at 5% so that's why I said "tied"
for 4th. Not sure this is an important point of discussion.
On Monday, July 8, 2019 at 9:39:10 AM UTC-4, Jan Mercl wrote:
>
>
>
> On Mon, Jul 8, 2019 at 3:33 PM Chris Passas > wrote:
We are all aware error handling was tied for 4th most common challenging
when working with Go in the 2018 survey.
There is not description of what about error handling. I'm sure I missed
the conversation but how did we get to the point of deciding it was the if
err!=nil that was the "challengin
