loading...

Discussions for Go 2

twitter logo github logo ・1 min read

The draft design discussions for Go 2 popped up in my feed recently and I felt that it would be worth re-posting to this community; I'm definitely going to provide some feedback and I'd encourage other Gophers to do the same!

P.S. Subscribe to Golang Weekly because it's awesome and always makes my Thursday when it hits my inbox. They also have a Twitter account you can follow.

twitter logo DISCUSS (6)
markdown guide
 

I made a blog post about the new Error Handling construct! I might work on the new Error Values tomorrow, and hopefully Generics within the next week.

I really like all three drafts, although I think the parentheses notation for generics is a bit hurtful for the eyes. Hoping that gets a different syntax

 
 

I really like the new handle and check, but I really can't see how the new contract based generics fits in with the idea of being a simple/stupid language.

 

Just as a quick follow-up, here is my submission for suggestions on the error handling. I'd love to drop submissions for all three and if I do, I'll follow up with a post with summaries of all three.

 
 

Hey tux0r, what is it that you mean with this comment? You link a random blog post with a single link to a post related to Go, mention actual failings of a programming language, without any context.

Wouldn't be more constructive to actually explain what you mean?

Thanks

Classic DEV Post from May 10 '19

What do you wish you knew about Developer Relations?

A conversation... what do DevRel professionals wish devs knew about their job? And what do devs wish they knew about DevRel?

John Forstmeier profile image
Build well