summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorOling Cat <olingcat@gmail.com>2013-12-11 09:49:28 +1100
committerOling Cat <olingcat@gmail.com>2013-12-11 09:49:28 +1100
commit205c103494b667023161d3939f088053abfce91f (patch)
treebec5243a45d49d5714a81e2a078f4f256fbdfc57 /doc
parent92da89e6ea59e5047ecb9dd03212838bc846ae92 (diff)
downloadgo-205c103494b667023161d3939f088053abfce91f.tar.gz
doc/effective_go.html: close some tags.
R=golang-dev, minux.ma CC=golang-dev https://codereview.appspot.com/37700043 Committer: Andrew Gerrand <adg@golang.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/effective_go.html4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/effective_go.html b/doc/effective_go.html
index f9199511a..207bd50c1 100644
--- a/doc/effective_go.html
+++ b/doc/effective_go.html
@@ -701,6 +701,7 @@ for _, value := range array {
<p>
The blank identifier has many uses, as described in <a href="#blank">a later section</a>.
+</p>
<p>
For strings, the <code>range</code> does more work for you, breaking out individual
@@ -2173,6 +2174,7 @@ A one-case type switch would do, but so would a <em>type assertion</em>.
A type assertion takes an interface value and extracts from it a value of the specified explicit type.
The syntax borrows from the clause opening a type switch, but with an explicit
type rather than the <code>type</code> keyword:
+</p>
<pre>
value.(typeName)
@@ -2463,6 +2465,8 @@ It has uses beyond those we've seen already.
<p>
The use of a blank identifier in a <code>for</code> <code>range</code> loop is a
special case of a general situation: multiple assignment.
+</p>
+
<p>
If an assignment requires multiple values on the left side,
but one of the values will not be used by the program,