On Wed, Nov 9, 2022 at 10:40 AM Gorka Guardiola <pau...@gmail.com> 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 wrap errors with other errors or check > different kinds of errors. > 3) Hopefully it does not disturb the flow of code to make it difficult to > read (it is similar to return, > not to exceptions, it is not thrown and caught). > > Maybe something like this has been proposed before, but I am not aware of it. > > This is an informal writeup, hopefully it is understandable enough, but if > not, feel free to ask any questions. > > Thoughts?
Seems related to https://go.dev/issue/54361, although due to inject it is not the same. Ian -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcVjb4D4cjy8-VUE2sKMc-Gr_n2%2BtDPENXN42UbGjcyi5g%40mail.gmail.com.
