The error handling in Go is fine I think. Some syntactic sugar may be nice, but not needed and makes the language slightly more complicated. Unions are still useful for many other cases though. What I would really like is to get away from runtime reflection and make compile time reflection the norm. Performance is really an important topic in more and more projects. Go generate is basically that but inside the tooling instead of the language itself. The tool directive shows they want to keep going into that direction. Fine for me. The rework of the JSON API is interesting. More performance and better behavior is great. Protobuf changes look good too, even though I haven't used it yet.
I wish json were more performant, it’s not hard to improve substantially. There’s a workaround for every deficiency in stdlib through a third-party package. But having stdlib on par with them out of the box in a consistent way would be really welcome.
As a recovering C++ developer, I *love* Go's error handling. I do not think it is broken and therefore needs no fixing.
Word!
same here man
catch (const std::exception& ex) { // log the error }
catch (const lib1::exception& ex) { // log the error }
catch (const otherlib::error e) { // log the error }
catch (...) { std::cerr
The error handling in Go is fine I think. Some syntactic sugar may be nice, but not needed and makes the language slightly more complicated. Unions are still useful for many other cases though.
What I would really like is to get away from runtime reflection and make compile time reflection the norm. Performance is really an important topic in more and more projects. Go generate is basically that but inside the tooling instead of the language itself. The tool directive shows they want to keep going into that direction. Fine for me.
The rework of the JSON API is interesting. More performance and better behavior is great. Protobuf changes look good too, even though I haven't used it yet.
Glorious evolution!
Great video, subbed
Subbed
btw did you notice gopls finally has type inference for generics
I wish json were more performant, it’s not hard to improve substantially. There’s a workaround for every deficiency in stdlib through a third-party package. But having stdlib on par with them out of the box in a consistent way would be really welcome.
Subbed... thank you! (get better, kids!)
watch?v=s7WNFzm3vjo