Go 2 Error Values draft implementation – planned for v1.13
godoc.org
godoc.org
https://go.googlesource.com/proposal/+/master/design/go2draf...
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)?
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.