Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
go
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
go
Commits
399a36a6
Commit
399a36a6
authored
Jan 15, 2013
by
Andrew Gerrand
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: fix various fragment links
R=dsymonds CC=golang-dev
https://golang.org/cl/7094058
parent
6d725e97
Changes
5
Hide whitespace changes
Inline
Side-by-side
Showing
5 changed files
with
8 additions
and
8 deletions
+8
-8
doc/articles/c_go_cgo.html
doc/articles/c_go_cgo.html
+2
-2
doc/articles/go_command.html
doc/articles/go_command.html
+1
-1
doc/articles/laws_of_reflection.html
doc/articles/laws_of_reflection.html
+1
-1
doc/code.html
doc/code.html
+2
-2
doc/go_faq.html
doc/go_faq.html
+2
-2
No files found.
doc/articles/c_go_cgo.html
View file @
399a36a6
...
...
@@ -149,9 +149,9 @@ is more complex than a single function call), as in this rewrite of
</p>
<p>
To build cgo packages, just use
<a
href=
"/cmd/go/#Compile_packages_and_dependencies"
>
"
To build cgo packages, just use
<a
href=
"/cmd/go/#
hdr-
Compile_packages_and_dependencies"
>
"
<code>
go build
</code>
"
</a>
or
<a
href=
"/cmd/go/#Compile_and_install_packages_and_dependencies"
>
"
<code>
go install
</code>
<a
href=
"/cmd/go/#
hdr-
Compile_and_install_packages_and_dependencies"
>
"
<code>
go install
</code>
"
</a>
as usual. The go tool recognizes the special
<code>
"C"
</code>
import and automatically
uses cgo for those files.
</p>
...
...
doc/articles/go_command.html
View file @
399a36a6
...
...
@@ -48,7 +48,7 @@ had to be installed in certain places, under certain names, using certain build
tools, in order to be used. That's understandable: that's the way it works in
most other languages. Over the last few years we consistently reminded people
about the
<code>
goinstall
</code>
command
(now replaced by
<a
href=
"/cmd/go/#Download_and_install_packages_and_dependencies"
><code>
go get
</code></a>
)
(now replaced by
<a
href=
"/cmd/go/#
hdr-
Download_and_install_packages_and_dependencies"
><code>
go get
</code></a>
)
and its conventions: first, that the import path is derived in a known way from
the URL of the source code; second, that the place to store the sources in
the local file system is derived in a known way from the import path; third,
...
...
doc/articles/laws_of_reflection.html
View file @
399a36a6
...
...
@@ -213,7 +213,7 @@ type: float64
You might be wondering where the interface is here, since the program looks
like it's passing the
<code>
float64
</code>
variable
<code>
x
</code>
, not an
interface value, to
<code>
reflect.TypeOf
</code>
. But it's there; as
<a
href=
"/pkg/reflect/#Type
.Type
Of"
>
godoc reports
</a>
, the signature of
<a
href=
"/pkg/reflect/#TypeOf"
>
godoc reports
</a>
, the signature of
<code>
reflect.TypeOf
</code>
includes an empty interface:
</p>
...
...
doc/code.html
View file @
399a36a6
...
...
@@ -406,7 +406,7 @@ ok example/newmath 0.165s
</pre>
<p>
Run
<code><a
href=
"/cmd/go/#Test_packages"
>
go help test
</a></code>
and see the
Run
<code><a
href=
"/cmd/go/#
hdr-
Test_packages"
>
go help test
</a></code>
and see the
<a
href=
"/pkg/testing/"
>
testing package documentation
</a>
for more detail.
</p>
...
...
@@ -486,7 +486,7 @@ is a list of external Go projects including programs and libraries.
<p>
For more information on using remote repositories with the
<code>
go
</code>
command, see
<code><a
href=
"/cmd/go/#Remote_import_path_syntax"
>
go help remote
</a></code>
.
<code><a
href=
"/cmd/go/#
hdr-
Remote_import_path_syntax"
>
go help remote
</a></code>
.
</p>
...
...
doc/go_faq.html
View file @
399a36a6
...
...
@@ -1263,7 +1263,7 @@ each closure shares that single variable. When the closure runs, it prints the
value of
<code>
v
</code>
at the time
<code>
fmt.Println
</code>
is executed,
but
<code>
v
</code>
may have been modified since the goroutine was launched.
To help detect this and other problems before they happen, run
<a
href=
"http://golang.org/cmd/go/#Run_go_tool_vet_on_packages"
><code>
go vet
</code></a>
.
<a
href=
"http://golang.org/cmd/go/#
hdr-
Run_go_tool_vet_on_packages"
><code>
go vet
</code></a>
.
</p>
<p>
...
...
@@ -1359,7 +1359,7 @@ builds a test binary, and runs it.
<p>
See the
<a
href=
"/doc/code.html"
>
How to Write Go Code
</a>
document,
the
<a
href=
"/pkg/testing/"
><code>
testing
</code></a>
package
and the
<a
href=
"/cmd/go/#Test_packages"
><code>
go test
</code></a>
subcommand for more details.
and the
<a
href=
"/cmd/go/#
hdr-
Test_packages"
><code>
go test
</code></a>
subcommand for more details.
</p>
<h3
id=
"testing_framework"
>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment