summaryrefslogtreecommitdiff
path: root/doc/go1.1.html
diff options
context:
space:
mode:
authorAndrew Gerrand <adg@golang.org>2013-10-09 07:05:43 +1100
committerAndrew Gerrand <adg@golang.org>2013-10-09 07:05:43 +1100
commit61384567d6f647fd3ab5f899f1ec1fa31495c117 (patch)
tree70135a6e5793132cb27a90f8ee7f7b44ceb233ee /doc/go1.1.html
parent1636013b370c4ce1f6d47eec947e70c508793d83 (diff)
downloadgo-61384567d6f647fd3ab5f899f1ec1fa31495c117.tar.gz
doc: fix a few broken links
R=golang-dev, r CC=golang-dev https://codereview.appspot.com/14494044
Diffstat (limited to 'doc/go1.1.html')
-rw-r--r--doc/go1.1.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/go1.1.html b/doc/go1.1.html
index a68664954..87d5f5c87 100644
--- a/doc/go1.1.html
+++ b/doc/go1.1.html
@@ -129,7 +129,7 @@ only an infinite "for" loop.
<p>
In Go 1.1, the rule about final "return" statements is more permissive.
It introduces the concept of a
-<a href="/ref/spec/#Terminating_statements"><em>terminating statement</em></a>,
+<a href="/ref/spec#Terminating_statements"><em>terminating statement</em></a>,
a statement that is guaranteed to be the last one a function executes.
Examples include
"for" loops with no condition and "if-else"
@@ -191,7 +191,7 @@ more than 2 billion elements on 64-bit platforms.
<em>Updating</em>:
Most programs will be unaffected by this change.
Because Go does not allow implicit conversions between distinct
-<a href="/ref/spec/#Numeric_types">numeric types</a>,
+<a href="/ref/spec#Numeric_types">numeric types</a>,
no programs will stop compiling due to this change.
However, programs that contain implicit assumptions
that <code>int</code> is only 32 bits may change behavior.