From 1843464f014c946c1663de76249267486887626f Mon Sep 17 00:00:00 2001 From: Joe Tsai Date: Mon, 1 Apr 2024 13:13:50 -0700 Subject: all: consistently use "IEEE 754" over "IEEE-754" There is no hyphen between the organization and the number. For example, https://standards.ieee.org/ieee/754/6210/ shows the string "IEEE 754-2019" and not "IEEE-754-2019". This assists in searching for "IEEE 754" in documentation and not missing those using "IEEE-754". Change-Id: I9a50ede807984ff1e2f17390bc1039f6a5d162e5 Reviewed-on: https://go-review.googlesource.com/c/go/+/575438 Run-TryBot: Joseph Tsai Reviewed-by: Robert Griesemer Auto-Submit: Joseph Tsai TryBot-Result: Gopher Robot TryBot-Bypass: Dmitri Shuralyov Reviewed-by: Ian Lance Taylor --- src/encoding/gob/doc.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/encoding') diff --git a/src/encoding/gob/doc.go b/src/encoding/gob/doc.go index 3f26ed8591..30e7978b7c 100644 --- a/src/encoding/gob/doc.go +++ b/src/encoding/gob/doc.go @@ -67,7 +67,7 @@ arbitrary precision unsigned integers. There is no int8, int16 etc. discrimination in the gob format; there are only signed and unsigned integers. As described below, the transmitter sends the value in a variable-length encoding; the receiver accepts the value and stores it in the destination variable. -Floating-point numbers are always sent using IEEE-754 64-bit precision (see +Floating-point numbers are always sent using IEEE 754 64-bit precision (see below). Signed integers may be received into any signed integer variable: int, int16, etc.; -- cgit v1.3