Skip to content

Commit ce16086

Browse files
ianlancetaylorgopherbot
authored andcommitted
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 <[email protected]> TryBot-Bypass: Ian Lance Taylor <[email protected]> Reviewed-by: Robert Griesemer <[email protected]> Auto-Submit: Ian Lance Taylor <[email protected]>
1 parent 795e779 commit ce16086

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/go_spec.html

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
<!--{
22
"Title": "The Go Programming Language Specification",
3-
"Subtitle": "Version of Aug 17, 2023",
3+
"Subtitle": "Version of Aug 18, 2023",
44
"Path": "/ref/spec"
55
}-->
66

@@ -4491,7 +4491,7 @@ <h3 id="Type_inference">Type inference</h3>
44914491
and for which no explicit type arguments is provided.
44924492
These type parameters are called <i>bound</i> type parameters.
44934493
For instance, in the <code>dedup</code> example above, the type parameters
4494-
<code>P</code> and <code>E</code> are bound to <code>dedup</code>.
4494+
<code>S</code> and <code>E</code> are bound to <code>dedup</code>.
44954495
An argument to a generic function call may be a generic function itself.
44964496
The type parameters of that function are included in the set of bound
44974497
type parameters.

0 commit comments

Comments
 (0)