spec: correct type parameter name used in example

Change-Id: I40595a3f598483d029473af465c756f8777ecc91
Reviewed-on: https://go-review.googlesource.com/c/go/+/520915
Reviewed-by: Ian Lance Taylor <iant@google.com>
TryBot-Bypass: Ian Lance Taylor <iant@google.com>
Reviewed-by: Robert Griesemer <gri@google.com>
Auto-Submit: Ian Lance Taylor <iant@google.com>
This commit is contained in:
Ian Lance Taylor 2023-08-18 09:44:16 -07:00 committed by Gopher Robot
parent 795e779610
commit ce16086345
1 changed files with 2 additions and 2 deletions

View File

@ -1,6 +1,6 @@
<!--{ <!--{
"Title": "The Go Programming Language Specification", "Title": "The Go Programming Language Specification",
"Subtitle": "Version of Aug 17, 2023", "Subtitle": "Version of Aug 18, 2023",
"Path": "/ref/spec" "Path": "/ref/spec"
}--> }-->
@ -4491,7 +4491,7 @@ the type parameters of the functions that need to be instantiated
and for which no explicit type arguments is provided. and for which no explicit type arguments is provided.
These type parameters are called <i>bound</i> type parameters. These type parameters are called <i>bound</i> type parameters.
For instance, in the <code>dedup</code> example above, the type parameters For instance, in the <code>dedup</code> example above, the type parameters
<code>P</code> and <code>E</code> are bound to <code>dedup</code>. <code>S</code> and <code>E</code> are bound to <code>dedup</code>.
An argument to a generic function call may be a generic function itself. An argument to a generic function call may be a generic function itself.
The type parameters of that function are included in the set of bound The type parameters of that function are included in the set of bound
type parameters. type parameters.