Go 2 Considered Harmful: https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.p...
You got me. Genuinely thought it was gonna be a critique.
So what is it? I'm on my phone and don't feel like downloadig a random PDF just for curiosity...
Go 2, here we come
11–20 of 534 posts
Re: Go 2, here we come
#12I'll be very sad if this goes the way of Perl 6
It won't. It's an explicit requirement that it will not. Or even a Python 3. I had a slide saying as such in an earlier presentation:
https://docs.google.com/presentation/d/1DmyTABhGLvN0m2uHktvk... (slide 140)
Ian had a good talk & doc about this too recently:
https://github.com/golang/proposal/blob/master/design/28221-...
Re: Go 2, here we come
#13Re: Go 2, here we come
#14Earlier quoted context omitted.
You got me. Genuinely thought it was gonna be a critique.
So what is it? I'm on my phone and don't feel like downloadig a random PDF just for curiosity...
It's a pun. "Go 2" -> "Go To". Dijkstra coined "considered harmful" with the paper (letter) on "Go To statement considered harmful".
Re: Go 2, here we come
#15Re: Go 2, here we come
#16I'll be very sad if this goes the way of Perl 6
At least Perl 6 is DOA and there's little confusion about it. The fiasco that was Python 3 was much worse for how drawn out it was.
Re: Go 2, here we come
#17Non-go user here. So what are the most desired fratures from Go 2 in the community? I remember something about generics not being supported.
Generics and errors are the things that come up most frequently in surveys.
Re: Go 2, here we come
#18I hope they keep the changes reasonable and do not introduce any breaking changes. I like the language as it is now and I'm very productive in it.
Well for the first round they are looking at:
1. Allowing generalized unicode identifiers. That is hardly likely to break anything except possibly some crazy edge cases that dont happen in real code.
2. Binary integer literals. (unlikely to break things)
3. allowing seperating groups of digits in a number with _ like 1_000_000 (unlikely to break anything)
4. Permit signed integers as shift counts (no need to cast ant int to a uint to use it in a shift expression. This won't break any existing code).
So at least this first round is quite unlikely to break anything in real use.
Re: Go 2, here we come
#19Hahah oh no, I literally started learning Go last night. Now what?
Re: Go 2, here we come
#20Non-go user here. So what are the most desired fratures from Go 2 in the community? I remember something about generics not being supported.
Helpful link from the text: https://github.com/golang/go/issues?q=is%3Aissue+is%3Aopen+l...
These are Go2 proposal PRs, sorted by upvotes.