On Sat, Nov 12, 2022 at 12:40 AM Mike Schinkel wrote:
> Hi G.,
>
> It takes guts to make a proposal in the Go community. Kudos for doing so.
>
Or recklessness :-). Thanks.
>
> However, the issue with this proposal for me is the issue I have with
> almost(?) every other proposal to handle erro
Hi G.,
It takes guts to make a proposal in the Go community. Kudos for doing so.
However, the issue with this proposal for me is the issue I have with
almost(?) every other proposal to handle errors in Go differently from what
Go currently allows. They all make the assumption that as soon as a
On Wed, Nov 9, 2022, 20:47 Ian Lance Taylor wrote:
> On Wed, Nov 9, 2022 at 10:40 AM Gorka Guardiola wrote:
>
> Seems related to https://go.dev/issue/54361, although due to inject it
> is not the same.
>
I hadn't seen that proposal.
>
It is similar in the sense that it is a more powerful retur
On Wed, Nov 9, 2022 at 10:40 AM Gorka Guardiola wrote:
>
> I have the following idea [1] for decluttering error handling in go. It looks
> similar to others already presented, but is is different in important ways:
>
> 1) It does not interfere with or use panic
> 2) Is general enough that one can
I have the following idea [1] for decluttering error handling in go. It
looks similar to others already presented, but is is different in important
ways:
1) It does not interfere with or use panic
2) Is general enough that one can wrap errors with other errors or check
different kinds of errors.
3
