🎊 We just announced an update for Go 2! This includes preliminary draft designs for generics, error handling, and error values. Read our blog and watch the video by @_rsc for more information. buff.ly/2okToPb

@golang @_rsc Nice! While the `handle err {}` block is interesting, will this have to always be defined within a local scope? What if I don't _know/think_ any errors will be returned in a code block but are. Can they be handled anyway by some default/top-level `handle err {}` block?

@golang @_rsc generics? end of go

@golang @_rsc I must admit I’ve been against the idea of Generics in Go for some time, but I do like the proposed idea of an explicit contract definition. Very elegant and appreciated.

@golang @_rsc Great! Still going through the drafts but I realized that to completely "grok" them, I might have to try to implement or, better, modify a few of my libraries to see what it entails, what are the pain points, confusing area and what not. How should I proceed?

@golang @_rsc Why the contracts. We have interfaces which they are contracts already.

@golang @_rsc Praise be

@golang @_rsc The handle keyword feels the same as what I dislike when using exceptions in other languages, having the error handling decoupled from the actions that provoked the error; even if it's within the same function, it feels weird

@golang @_rsc As io.Reader Read() may return a non-zero int and a non-nil error at the same time, how to use check/handle with Read()? Or is that means Read() should return 0 when err != nil?

@golang @_rsc Awesome. I was worried Go was getting too fast. But with generics, now Im not worried anymore

@golang @_rsc come on, the first thing I have learned in programming is that go2 is evil and should be avoided at all cost

@golang @_rsc Future of Go 10 : [ [ [ ] ] ] func ( ) ( ) ( ) fn( a ) ( b ) ( c ) ( d ) ( ) ( ) ( ) (string, error) {} add more brackets as you want. and function fn can do everything.

@golang @_rsc Very true that Go 2 is the most capable for error handling. Remembering my Go project on this #error handling tweet. Can't forget Go’s way of handling errors @golang @golang_news @golangweekly bacancytechnology.com/blog/golang-er…

@golang @sale87 U 2018. su shvatili sa im ipak trebaju generics... iznerviram se kad god pomislim na zadrte ljude koji su govorili “ali zapravo ti ne trebaju”, ne matori, trebaju mi

@golang @_rsc With generics, it's time for some decent std collection structures for golang

@golang @_rsc 🎉🎉🎉🎉🎉

@golang @_rsc TarsGo: A high performance microservice framework in golang： medium.com/@sandyskiescha…

@golang @_rsc Opencrypter loves go

@golang @_rsc Contracts are the most interesting part of the announcement to me. It seems they intend to check the contracts at compile time, by limiting the language features allowed in them. Given the emphasis on fast compilation in Go I am curious about their solution.

@golang @_rsc

@golang @_rsc Can you have multiple handle blocks in a function, since you might have multiple error types? func doWidget() { handle err {...} handle package.MagicError {...} handle int {...} ...real code... }

@golang @_rsc Great news for today! \o/

@golang @_rsc I never understood generics, let alone the need for them. I hope Go can apply some pragmatism here and keep it simple

@golang @_rsc The error handling example here is horrible: go.googlesource.com/proposal/+/mas… if you write the right error messages the problem of repetition disappears.

@golang @kelseyhightower @_rsc It's time to finally fix that no-semicolons thing

@golang @_rsc Holy shit! Generics is finally happening!!! 😊