From 369d1083a74b6a965a33510489ab381d937812ae Mon Sep 17 00:00:00 2001 From: Robert Griesemer Date: Fri, 24 Mar 2017 09:19:46 -0700 Subject: [PATCH] spec: for non-constant map keys, add reference to evaluation order section The section on map literals mentions constant map keys but doesn't say what happens for equal non-constant map keys - that is covered in the section on evaluation order. Added respective link for clarity. Fixes #19689. Change-Id: If9a5368ba02e8250d4bb0a1d60d0de26a1f37bbb Reviewed-on: https://go-review.googlesource.com/38598 Reviewed-by: Rob Pike Reviewed-by: Matthew Dempsky Reviewed-by: Ian Lance Taylor --- doc/go_spec.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/go_spec.html b/doc/go_spec.html index fa95caca3a..5ee8287889 100644 --- a/doc/go_spec.html +++ b/doc/go_spec.html @@ -1,6 +1,6 @@ @@ -2295,7 +2295,8 @@ The key is interpreted as a field name for struct literals, an index for array and slice literals, and a key for map literals. For map literals, all elements must have a key. It is an error to specify multiple elements with the same field name or -constant key value. +constant key value. For non-constant map keys, see the section on +evaluation order.

-- 2.48.1