Let me ask it differently what is going to happen with all the Go2 labeled issues on github? For me experience report is nothing different then a github issue and also nobody of the go team will be able to handle all the incoming false positives of people like me that think have a great idea but actually isn't or already has been addressed. Sorry I just prefer the other way around, the go team makes a report looking at golang code on github and question on stackoverflow and make proposal to clean up standard library and improve the language. The same way to go team did with Go 1.9 and type aliases. Reporting the issue listen to feedback and implement it. Go2 should be a breath of fresh air to finally undo a few mistakes and clean things up, it should definitely not be a publicity stunt and just leave all the mistakes in to be backward compatible.
On Monday, July 17, 2017 at 7:06:15 AM UTC+2, Nathan Kerr wrote: > > The active work for Go2 right now is gathering experience reports > <http://golang.org/wiki/ExperienceReports>. Most of the changes resulting > from these reports will land in Go1.x. It is expected that Go2 will only > have a few major changes that will not be compatible with Go1. It is also > possible there will be none (and Go1.20 will be called Go2) > > The Go2 label in the issue tracker has meant, more or less, that the > issue/proposal was something that could't be considered for Go1, usually > because it would be the Go1 compatibility promise, but should be kept track > of. > > Apple didn't mention Swift because Apple doesn't mention things it is > working on. Working in private and then releasing when things are ready is > how Apple does things. > > On Monday, July 17, 2017 at 5:42:34 AM UTC+2, Gert wrote: >> >> There are so many >> https://github.com/golang/go/issues?q=is%3Aissue+is%3Aopen+go2+label%3AGo2 >> proposals already I can barely figure out if feature x y or z is already >> asked. >> >> Can we have a Go2 branch / milestone please? PS now that you announced >> toward-go2 you are going to actively work on Go2 right? Its not some kind >> of lets try to trick developers to keep using Go who are looking for >> alternatives because they made a Go2 proposal many years ago and gave up >> hope right? Don't get me wrong I love Go but I hate false promises or >> making plans ridiculous far in the future. Not saying Go2 can't take a long >> time to make, just saying i would like to see small bits of code emerging >> on a weekly bases we can test and play around with and give feedback on >> real things not just imaginary ideas :) If you can't make a Go2 branch yet >> and more important things need to be done first on Go1 I understand >> completely, but once you pull the Go2 card companies will pull back and >> start waiting for Go2. Its the number one reason Apple didn't mention a >> single word about Swift until they could deliver a fully functioning >> compiler just because of that reasons to not jeopardise developers stop >> learning objective c and waiting for Swift >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
