qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-11 22:40:22 -07:00
Code Releases Activity

doc: fix spec links in Go 1.13 release notes

Browse Source 
When reading tip.golang.org/doc/go1.13.html, the spec links in
the "Changes to the language" section should point to the updated
spec, not the old one.

Change-Id: I6b13ca0b4c722ed52b84a12a680bece876a4e478
Reviewed-on: https://go-review.googlesource.com/c/go/+/184118
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
This commit is contained in:
Diogo Pinela 2019-06-27 22:19:15 +01:00 committed by Brad Fitzpatrick
parent b97ec8e57f
commit 67f181bfd8
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/go1.13.html
View File

@ -41,13 +41,13 @@ Do not send CLs removing the interior tags from such phrases.
Go 1.13 supports a more uniform and modernized set of number literal prefixes. Go 1.13 supports a more uniform and modernized set of number literal prefixes.
<ul> <ul>
<li> <li>
<a href="https://golang.org/ref/spec#Integer_literals">Binary integer literals</a>: <a href="/ref/spec#Integer_literals">Binary integer literals</a>:
The prefix <code>0b</code> or <code>0B</code> indicates a binary integer literal The prefix <code>0b</code> or <code>0B</code> indicates a binary integer literal
such as <code>0b1011</code>. such as <code>0b1011</code>.
</li> </li>
<li> <li>
<a href="https://golang.org/ref/spec#Integer_literals">Octal integer literals</a>: <a href="/ref/spec#Integer_literals">Octal integer literals</a>:
The prefix <code>0o</code> or <code>0O</code> indicates an octal integer literal The prefix <code>0o</code> or <code>0O</code> indicates an octal integer literal
such as <code>0o660</code>. such as <code>0o660</code>.
The existing octal notation indicated by a leading <code>0</code> followed by The existing octal notation indicated by a leading <code>0</code> followed by
@ -55,7 +55,7 @@ Do not send CLs removing the interior tags from such phrases.
</li> </li>
<li> <li>
<a href="https://golang.org/ref/spec#Floating-point_literals">Hexadecimal floating point literals</a>: <a href="/ref/spec#Floating-point_literals">Hexadecimal floating point literals</a>:
The prefix <code>0x</code> or <code>0X</code> may now be used to express the mantissa of a The prefix <code>0x</code> or <code>0X</code> may now be used to express the mantissa of a
floating-point number in hexadecimal format such as <code>0x1.0p-1021</code>. floating-point number in hexadecimal format such as <code>0x1.0p-1021</code>.
A hexadecimal floating-point number must always have an exponent, written as the letter A hexadecimal floating-point number must always have an exponent, written as the letter
@ -64,7 +64,7 @@ Do not send CLs removing the interior tags from such phrases.
</li> </li>
<li> <li>
<a href="https://golang.org/ref/spec#Imaginary_literals">Imaginary literals</a>: <a href="/ref/spec#Imaginary_literals">Imaginary literals</a>:
The imaginary suffix <code>i</code> may now be used with any (binary, decimal, hexadecimal) The imaginary suffix <code>i</code> may now be used with any (binary, decimal, hexadecimal)
integer or floating-point literal. integer or floating-point literal.
</li> </li>
@ -80,7 +80,7 @@ Do not send CLs removing the interior tags from such phrases.
<p> <p>
Per the <a href="https://github.com/golang/proposal/blob/master/design/19113-signed-shift-counts.md">signed shift counts proposal</a> Per the <a href="https://github.com/golang/proposal/blob/master/design/19113-signed-shift-counts.md">signed shift counts proposal</a>
Go 1.13 removes the restriction that a <a href="https://golang.org/ref/spec#Operators">shift count</a> Go 1.13 removes the restriction that a <a href="/ref/spec#Operators">shift count</a>
must be unsigned. This change eliminates the need for many artificial <code>uint</code> conversions, must be unsigned. This change eliminates the need for many artificial <code>uint</code> conversions,
solely introduced to satisfy this (now removed) restriction of the <code>&lt;&lt;</code> and <code>&gt;&gt;</code> operators. solely introduced to satisfy this (now removed) restriction of the <code>&lt;&lt;</code> and <code>&gt;&gt;</code> operators.
</p> </p>