Commit 38d7bcf5 authored by Rob Pike's avatar Rob Pike

go spec: fix up HTML glitches.

Fixes #1786.

R=gri, adg
CC=golang-dev
https://golang.org/cl/4517043
parent 121b428a
......@@ -1972,7 +1972,7 @@ math.Sin
<p>
<span class="alert">TODO: Unify this section with Selectors - it's the same syntax.</span>
</p>
--->
-->
<h3 id="Composite_literals">Composite literals</h3>
......@@ -2340,7 +2340,7 @@ p.M0 // ((*p).T0).M0
<span class="alert">
TODO: Specify what happens to receivers.
</span>
--->
-->
<h3 id="Indexes">Indexes</h3>
......@@ -3080,7 +3080,7 @@ Receiving from a <code>nil</code> channel causes a
<span class="alert">TODO: Probably in a separate section, communication semantics
need to be presented regarding send, receive, select, and goroutines.</span>
</p>
--->
-->
<h3 id="Method_expressions">Method expressions</h3>
......@@ -3457,7 +3457,7 @@ Also it may be possible to make typed constants more like variables, at the cost
overflow etc. errors being caught.
</span>
</p>
--->
-->
<h3 id="Order_of_evaluation">Order of evaluation</h3>
......@@ -4029,7 +4029,7 @@ iteration values for each entry will be produced at most once.
<li>
For channels, the iteration values produced are the successive values sent on
the channel until the channel is closed
<a href="#Close"><code>close</code>).
<a href="#Close"><code>close</code></a>).
</li>
</ol>
......@@ -4255,7 +4255,7 @@ TODO: Language about result parameters needs to go into a section on
function/method invocation<br />
</span>
</p>
--->
-->
<h3 id="Break_statements">Break statements</h3>
......@@ -4334,7 +4334,7 @@ is erroneous because the jump to label <code>L</code> skips
the creation of <code>v</code>.
<!---
(<span class="alert">TODO: Eliminate in favor of used and not set errors?</span>)
--->
-->
</p>
<h3 id="Fallthrough_statements">Fallthrough statements</h3>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment