CL 374215 resolves this issue, but isn't to be submitted until Go 1.18 is released.
Since there's nothing more to do here during 1.18 cycle, moving to 1.19 and adding early-in-cycle. Actually, we also have issue #49938 tracking this task, so we can can close this one.
Also update the existing generics FAQ.
For golang/go#48274Fixesgolang/go#49938
Change-Id: Id87dbf43f4a151abb7c2c2f6309fc8ee3c947aa1
Reviewed-on: https://go-review.googlesource.com/c/website/+/374215
Reviewed-by: Russ Cox <rsc@golang.org>
Run-TryBot: Dmitri Shuralyov <dmitshur@google.com>
Trust: DO NOT USE <iant@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Many sections of the FAQ need tweaking, a few need replacement. Update before release.
For example, here's a question there that needs to be rethought: "Why does Go not have generic types?"
The text was updated successfully, but these errors were encountered: