Robert Griesemer 4703546a29 spec: add missing optional type arguments after TypeName in syntax ... Types may be generic, so each occurrence of a TypeName may be followed by optional type arguments. Add the missing syntactic (EBNF) factor. The syntax of type names followed by type arguments matches the syntax of operand names followed by type arguments (operands may also be types, or generic functions, among other things). This opens the door to factoring out this shared syntax, but it will also require some adjustments to prose to make it work well. Leaving for another change. Fixes #53240. Change-Id: I15212225c28b27f7621e3ca80dfbd131f6b7eada Reviewed-on: https://go-review.googlesource.com/c/go/+/411918 Reviewed-by: Ian Lance Taylor <iant@google.com> Reviewed-by: Robert Griesemer <gri@google.com>		2022-06-13 19:06:49 +00:00
..
asm.html	doc/asm: fix HTML markup	2021-09-10 17:15:37 +00:00
go1.17_spec.html	spec: fix a broken link	2021-11-11 19:44:13 +00:00
go1.19.html	doc/go1.19: add a release note for module indexing	2022-06-13 18:56:11 +00:00
go_mem.html	doc: fix typos in Go memory model	2022-06-10 22:10:29 +00:00
go_spec.html	spec: add missing optional type arguments after TypeName in syntax	2022-06-13 19:06:49 +00:00