Go 2 Error Values draft implementation – planned for v1.13

https://godoc.org/golang.org/x/exp/errors

by networkimprov • 8 years ago

21 7 8 years ago

godoc.org

networkimprov2• 8 years ago

It has dropped the dependency on Go 2 Generics described in the "draft design".

https://go.googlesource.com/proposal/+/master/design/go2draf...

zelly• 8 years ago

Wow, looks like Go 2 might actually be usable.

pstuart• 8 years ago

Go 1 has been rather usable for many of us so far :-)

ernst_klim• 8 years ago

They still suggest to return a pair of values on both error and non-error case and try to figure out, if your error value invalidates the main return value or not, instead of adding sum-types. Not to mention that error still does not signify statically its type.

How is this useful? Why do go people try to reinvent the wheel for a problem long solved (with the result monad, exceptions, algebraic effects etc)?

cyrusaf• 8 years ago

Sum types would add much needed compiler safety to returned errors and optional values. We often see nil pointer dereferences during runtime due to the usage of pointers as optional types.

coldtea• 8 years ago

How is this useful? Why do go people try to reinvent the wheel for a problem long solved

They think their designs are superior/simpler. Even when an approach's faults are acknowledged, they patch them with the same basic core logic (e.g. keeping arbitrary error signaling per function based on multiple return values), and add more accidental complexity.

Go 2 Error Values draft implementation – planned for v1.13

Related Stories