News for hackers. Stuff that matters.
Re:Error stack traces in Go with x/xerror by makapuf on Tuesday August 24, 2021 @02:38AM (#28285759)
There has been a go2 proposal for better error handling, so there is no issue trying to improve things or adding needed features. But things go slowly and must be discussed and vetted before being accepted because the language has few features and they will stick so the filter is quite high. See generics, it took a long time but its coming.
Re:Error stack traces in Go with x/xerror by tsimionescu on Tuesday August 24, 2021 @05:59AM (#28286811)
The proposal for better error handling was rejected, as far as I'm aware. Generics needlessly repeated the mistakes of Java and C# in coming out years too late.
Re:Error stack traces in Go with x/xerror by makapuf on Tuesday August 24, 2021 @07:52AM (#28287572)
I kind of agree, it's better to have generics from the start (we'll see if there are difficulties added), and the error handling was rejected. But the fact that those proposals have been proposed, discussed, studied and for one of them accepted show that the language can evolve.