From 1aaf1b219a44feaeaa1d737b5ea82202e9dbd5de Mon Sep 17 00:00:00 2001
From: Robert Griesemer <gri@golang.org>
Date: Fri, 2 Jun 2023 09:29:07 -0700
Subject: [PATCH] spec: clarify min/max rules for numeric arguments (exclude
 NaNs)

Fixes #60570.

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

diff --git a/doc/go_spec.html b/doc/go_spec.html
index 2caf274ed0..bcb06e72ff 100644
--- a/doc/go_spec.html
+++ b/doc/go_spec.html
@@ -1,6 +1,6 @@
 <!--{
 	"Title": "The Go Programming Language Specification",
-	"Subtitle": "Version of May 25, 2023",
+	"Subtitle": "Version of June 6, 2023",
 	"Path": "/ref/spec"
 }-->
 
@@ -7563,7 +7563,7 @@ t := max("", "foo", "bar")  // t == "foo" (string kind)
 </pre>
 
 <p>
-For numeric arguments, <code>min</code> and <code>max</code> are
+For numeric arguments, assuming all NaNs are equal, <code>min</code> and <code>max</code> are
 commutative and associative:
 </p>
 
-- 
2.50.0