From 8219848c944c7603df349775de66093af64f0fd4 Mon Sep 17 00:00:00 2001
From: Robert Griesemer <gri@golang.org>
Date: Wed, 12 Jun 2024 14:28:30 -0700
Subject: [PATCH] spec: allow range-over-func to omit iteration variables

For #65236.

Change-Id: I5a11811cc52467ea4446db29c3f86b119f9b2409
Reviewed-on: https://go-review.googlesource.com/c/go/+/592295
Reviewed-by: Robert Griesemer <gri@google.com>
Auto-Submit: Robert Griesemer <gri@google.com>
TryBot-Bypass: Robert Griesemer <gri@google.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
---
 doc/go_spec.html | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/doc/go_spec.html b/doc/go_spec.html
index d1ca6722e1..c1d3360ef6 100644
--- a/doc/go_spec.html
+++ b/doc/go_spec.html
@@ -1,6 +1,6 @@
 <!--{
 	"Title": "The Go Programming Language Specification",
-	"Subtitle": "Language version go1.23 (June 4, 2024)",
+	"Subtitle": "Language version go1.23 (June 12, 2024)",
 	"Path": "/ref/spec"
 }-->
 
@@ -6733,8 +6733,6 @@ to generate iteration values this way for each <code>yield</code> call until
 <code>f</code> returns.
 If the loop body terminates (such as by a <code>break</code> statement),
 <code>yield</code> returns false and must not be called again.
-The number of iteration variables must match the number and order of arguments
-to <code>yield</code>.
 </li>
 </ol>
 
-- 
2.48.1