mirror of
https://github.com/golang/go
synced 2024-11-21 19:14:44 -07:00
go_tutorial: change wording slightly and sync .txt and .html post-gofmt
Fixes #1211. R=r, r2 CC=golang-dev https://golang.org/cl/2635041
This commit is contained in:
parent
64cc5be4ad
commit
7de5e6e84d
@ -531,7 +531,7 @@ object. We could write
|
|||||||
return n
|
return n
|
||||||
</pre>
|
</pre>
|
||||||
<p>
|
<p>
|
||||||
but for simple structures like <code>File</code> it's easier to return the address of a nonce
|
but for simple structures like <code>File</code> it's easier to return the address of a
|
||||||
composite literal, as is done here on line 21.
|
composite literal, as is done here on line 21.
|
||||||
<p>
|
<p>
|
||||||
We can use the factory to construct some familiar, exported variables of type <code>*File</code>:
|
We can use the factory to construct some familiar, exported variables of type <code>*File</code>:
|
||||||
|
@ -420,7 +420,7 @@ object. We could write
|
|||||||
n.name = name
|
n.name = name
|
||||||
return n
|
return n
|
||||||
|
|
||||||
but for simple structures like "File" it's easier to return the address of a nonce
|
but for simple structures like "File" it's easier to return the address of a
|
||||||
composite literal, as is done here on line 21.
|
composite literal, as is done here on line 21.
|
||||||
|
|
||||||
We can use the factory to construct some familiar, exported variables of type "*File":
|
We can use the factory to construct some familiar, exported variables of type "*File":
|
||||||
|
Loading…
Reference in New Issue
Block a user