On Mon, Oct 22, 2018 at 12:31 PM Liam <networkimp...@gmail.com> wrote:
>
> You might want to read the links on the feedback wiki, if you haven't already:
> https://github.com/golang/go/wiki/Go2ErrorHandlingFeedback
>
> Quite a lot of them suggest named handlers.
One difference in this proposal is that handler err { } defines both a
handler for err, and an error variable err, so if the handler did not
handle the error, the execution still continues with an err variable
containing the unhandled error.
I'll add a link to the gist under the "labeled error handlers"
section, that seems to be the closest topic.
>
> Feel free to add your gist link to the wiki!
>
> On Monday, October 22, 2018 at 7:33:38 AM UTC-7, Burak Serdar wrote:
>>
>> I read the error handling proposal recently, and although I like it in
>> general, I don't like the fact that it hides the actual error
>> variables from the flow. Also, I think the error chaining method as
>> described in the proposal is not very useful. So I came up with this
>> suggestion:
>>
>> https://gist.github.com/bserdar/4c728f85ca30de25a433e84ad5a065a1
>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
