On Mon, Oct 29, 2018 at 8:26 PM DrGo wrote:
>
>
> As many have pointed out, the check keyword has several shortcomings the most
> important for me are that:
> (1) it obscures the change in workflow and (2) it treats error values
> differently than all other values.
>
> Overall, I do not think t
What I like about error handling in Go is that errors are just values. Like
any other values, they can be transparently stored, aggregated, passed
around and used, among other things, to explicitly change program flow.
That is why I am on the whole satisfied by Go 1's approach and a bit
concern
