mirror of
https://github.com/golang/go
synced 2024-11-25 01:57:56 -07:00
doc: add a bunch of missing <p> tags
R=golang-dev, gri CC=golang-dev https://golang.org/cl/5707065
This commit is contained in:
parent
6652b0b866
commit
c50074e510
@ -323,7 +323,7 @@ foo_amd64.go
|
||||
foo_arm.go
|
||||
</pre>
|
||||
|
||||
describes a package that builds on
|
||||
<p>describes a package that builds on
|
||||
different architectures by parameterizing the file name with
|
||||
<code>$GOARCH</code>.</p>
|
||||
|
||||
|
@ -1617,40 +1617,49 @@ Now we have the missing piece we needed to explain the design of
|
||||
the <code>append</code> built-in function. The signature of <code>append</code>
|
||||
is different from our custom <code>Append</code> function above.
|
||||
Schematically, it's like this:
|
||||
</p>
|
||||
<pre>
|
||||
func append(slice []<i>T</i>, elements...T) []<i>T</i>
|
||||
</pre>
|
||||
<p>
|
||||
where <i>T</i> is a placeholder for any given type. You can't
|
||||
actually write a function in Go where the type <code>T</code>
|
||||
is determined by the caller.
|
||||
That's why <code>append</code> is built in: it needs support from the
|
||||
compiler.
|
||||
</p>
|
||||
<p>
|
||||
What <code>append</code> does is append the elements to the end of
|
||||
the slice and return the result. The result needs to be returned
|
||||
because, as with our hand-written <code>Append</code>, the underlying
|
||||
array may change. This simple example
|
||||
</p>
|
||||
<pre>
|
||||
x := []int{1,2,3}
|
||||
x = append(x, 4, 5, 6)
|
||||
fmt.Println(x)
|
||||
</pre>
|
||||
<p>
|
||||
prints <code>[1 2 3 4 5 6]</code>. So <code>append</code> works a
|
||||
little like <code>Printf</code>, collecting an arbitrary number of
|
||||
arguments.
|
||||
</p>
|
||||
<p>
|
||||
But what if we wanted to do what our <code>Append</code> does and
|
||||
append a slice to a slice? Easy: use <code>...</code> at the call
|
||||
site, just as we did in the call to <code>Output</code> above. This
|
||||
snippet produces identical output to the one above.
|
||||
</p>
|
||||
<pre>
|
||||
x := []int{1,2,3}
|
||||
y := []int{4,5,6}
|
||||
x = append(x, y...)
|
||||
fmt.Println(x)
|
||||
</pre>
|
||||
<p>
|
||||
Without that <code>...</code>, it wouldn't compile because the types
|
||||
would be wrong; <code>y</code> is not of type <code>int</code>.
|
||||
</p>
|
||||
|
||||
<h2 id="initialization">Initialization</h2>
|
||||
|
||||
|
@ -1613,40 +1613,49 @@ Now we have the missing piece we needed to explain the design of
|
||||
the <code>append</code> built-in function. The signature of <code>append</code>
|
||||
is different from our custom <code>Append</code> function above.
|
||||
Schematically, it's like this:
|
||||
</p>
|
||||
<pre>
|
||||
func append(slice []<i>T</i>, elements...T) []<i>T</i>
|
||||
</pre>
|
||||
<p>
|
||||
where <i>T</i> is a placeholder for any given type. You can't
|
||||
actually write a function in Go where the type <code>T</code>
|
||||
is determined by the caller.
|
||||
That's why <code>append</code> is built in: it needs support from the
|
||||
compiler.
|
||||
</p>
|
||||
<p>
|
||||
What <code>append</code> does is append the elements to the end of
|
||||
the slice and return the result. The result needs to be returned
|
||||
because, as with our hand-written <code>Append</code>, the underlying
|
||||
array may change. This simple example
|
||||
</p>
|
||||
<pre>
|
||||
x := []int{1,2,3}
|
||||
x = append(x, 4, 5, 6)
|
||||
fmt.Println(x)
|
||||
</pre>
|
||||
<p>
|
||||
prints <code>[1 2 3 4 5 6]</code>. So <code>append</code> works a
|
||||
little like <code>Printf</code>, collecting an arbitrary number of
|
||||
arguments.
|
||||
</p>
|
||||
<p>
|
||||
But what if we wanted to do what our <code>Append</code> does and
|
||||
append a slice to a slice? Easy: use <code>...</code> at the call
|
||||
site, just as we did in the call to <code>Output</code> above. This
|
||||
snippet produces identical output to the one above.
|
||||
</p>
|
||||
<pre>
|
||||
x := []int{1,2,3}
|
||||
y := []int{4,5,6}
|
||||
x = append(x, y...)
|
||||
fmt.Println(x)
|
||||
</pre>
|
||||
<p>
|
||||
Without that <code>...</code>, it wouldn't compile because the types
|
||||
would be wrong; <code>y</code> is not of type <code>int</code>.
|
||||
</p>
|
||||
|
||||
<h2 id="initialization">Initialization</h2>
|
||||
|
||||
|
@ -1524,7 +1524,9 @@ declaration should present the same order as <code>:=</code> so
|
||||
<pre>
|
||||
var a uint64 = 1
|
||||
</pre>
|
||||
<p>
|
||||
has the same effect as
|
||||
</p>
|
||||
<pre>
|
||||
a := uint64(1)
|
||||
</pre>
|
||||
|
@ -696,10 +696,11 @@ using a receiver of that type.
|
||||
|
||||
<h3 id="Boolean_types">Boolean types</h3>
|
||||
|
||||
<p>
|
||||
A <i>boolean type</i> represents the set of Boolean truth values
|
||||
denoted by the predeclared constants <code>true</code>
|
||||
and <code>false</code>. The predeclared boolean type is <code>bool</code>.
|
||||
|
||||
</p>
|
||||
|
||||
<h3 id="Numeric_types">Numeric types</h3>
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user