3 ms·

i use this a lot if error.Is(err, sql.ErrNoRow) { return status.Error(codes.NotFound, "foo does not exist") } srv.log.Err(err).Msg("failed to load foo") retu

by hknmtt 4y ago

i use this a lot if error.Is(err, sql.ErrNoRow) { return status.Error(codes.NotFound, "foo does not exist") } srv.log.Err(err).Msg("failed to load foo") return status.Error(codes.InternalError, "") True, that checking for more than one error type is very sparse but i still like the go errors the way they are.

nprateem 4y ago
There's nothing special about having different return types. Every language I can recall with throwable errors supports them, they just don't waste developer's time by manually bubbling them up the call stack.
- hknmtt 4y ago
  you can always panic/recover to get the throw/catch behavior