> error handling in Go is convoluted Is it worse than in C that there is no concept at all? Is it better that everyone is on their own to do it their own way e

> error handling in Go is convoluted Is it worse than in C that there is no concept at all? Is it better that everyone is on their own to do it their own way every time? I’m not above making the eaiser, but to your point when I see their example of: double* q = malloc(something); defer [qp = &q]{ free(*qp); }; That doesn’t look like the C that I know.