aboutsummaryrefslogtreecommitdiff
path: root/doc/go_spec.html
diff options
context:
space:
mode:
authorDaniel Frederick Crisman <daniel@crisman.org>2023-04-10 23:14:56 +0000
committerGopher Robot <gobot@golang.org>2023-04-11 17:02:02 +0000
commit6e8eec7328d8526f377c69076d3c84ffb7bf89be (patch)
treed28d729978782093de7948ffaab3e40d858212fb /doc/go_spec.html
parent8adfe35649691d1c9be1bfee3912d8619af6f210 (diff)
downloadgo-6e8eec7328d8526f377c69076d3c84ffb7bf89be.tar.gz
go-6e8eec7328d8526f377c69076d3c84ffb7bf89be.zip
doc: add missing oxford comma in Constants
In the language specification under "Constants" the lists matching default types to untyped contstant types is missing an Oxford comma in the first list. I found a number of other places in the spec and #23442 that use the Oxford comma to support its use. Add missing Oxford comma in Constants default type list. Change-Id: I4562d692610334bc82452db076145d2414617a04 GitHub-Last-Rev: 8acdb60d6e255f73fdeb908d2540d4ee35db3fd7 GitHub-Pull-Request: golang/go#59528 Reviewed-on: https://go-review.googlesource.com/c/go/+/483555 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Robert Griesemer <gri@google.com> Reviewed-by: Ian Lance Taylor <iant@google.com> Run-TryBot: Ian Lance Taylor <iant@google.com> Auto-Submit: Ian Lance Taylor <iant@google.com>
Diffstat (limited to 'doc/go_spec.html')
-rw-r--r--doc/go_spec.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/go_spec.html b/doc/go_spec.html
index 8aea636c6b..9f685d1f1f 100644
--- a/doc/go_spec.html
+++ b/doc/go_spec.html
@@ -690,7 +690,7 @@ constant is implicitly converted in contexts where a typed value is required,
for instance, in a <a href="#Short_variable_declarations">short variable declaration</a>
such as <code>i := 0</code> where there is no explicit type.
The default type of an untyped constant is <code>bool</code>, <code>rune</code>,
-<code>int</code>, <code>float64</code>, <code>complex128</code> or <code>string</code>
+<code>int</code>, <code>float64</code>, <code>complex128</code>, or <code>string</code>
respectively, depending on whether it is a boolean, rune, integer, floating-point,
complex, or string constant.
</p>