On Mon, Oct 11, 2021 at 12:59 AM nil...@gmail.com <nile...@gmail.com> wrote: > > I totally understand that nothing is guaranteed. Just wondering what is Go > team's release policy regarding the deadline. Is that a hard deadline? I > guess the generics support is the biggest component in 1.18 (and also the one > many people have been waiting for long :) ), if something unexpected happens > to it close to the planned release date, will the Go team be willing to delay > the release for a couple of weeks to allow generics to be included or the > current release policy would require the team to disable the generics in 1.18 > to ship the 1.18 on time?
It's difficult to answer these kinds of questions as precisely as one might wish. Go is an open source project with no paying customers. We have policies that we do our best to follow, but they're a bit like the pirate code: more what you'd call guidelines than actual rules. In the case of conflicting plans we'll try to come to some consensus as to how best to proceed. I'll note that for the last few years almost every release has been a week or two late, so the release date is definitely not a hard deadline. But a big decision like pulling generics out would most likely be made well ahead of the release date. Ian > On Monday, October 11, 2021 at 12:26:35 PM UTC+8 Ian Lance Taylor wrote: >> >> On Sun, Oct 10, 2021 at 2:55 AM nil...@gmail.com <nil...@gmail.com> wrote: >> > >> > We are really excited about the coming generics support in Go, our test >> > drive of the generics support in 1.17 is so far pretty positive and it >> > would also allow us to immediately delete tens of thousands lines of code >> > from our main project. >> > >> > Our understanding is that Go team's current plan is to have the generics >> > support enabled by default in the 1.18 release scheduled for Feb 2022. The >> > question we are facing now is how much certainty we have on that. I mean >> > if generics could get delayed until 1.19, which would be 10 months from >> > now, then we should probably wait rather than switching to the full use of >> > generics now. >> > >> > Could someone from the Go team provide us some guidance please? Shall we >> > wait until the coming code freeze or maybe beta1 to expect more >> > clarification? >> >> The current expectation is that Go 1.18 will support generics. The >> tip Go compiler already supports generics. There are bugs, but as >> they are reported they are being fixed. It is reasonably likely that >> some generics corner cases will not compile in Go 1.18, but the >> expectation is that straightforward uses of generics will work as >> expected. It is also likely that performance in Go 1.18 will not be >> as good as it will be in later releases. >> >> Of course, it's impossible to guarantee this. Something completely >> unexpected could happen. But that is the expectation. Hope this >> helps. >> >> Ian > > -- > 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 golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/51357b46-a8cb-4f08-a945-a5c283a7d977n%40googlegroups.com. -- 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 golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcURAkQqaZEg6RvSGJ1N1gmrwv8j0n-a6q8zfw5UT1tYnA%40mail.gmail.com.
