$ to represent the command prompt.
-Install Go (see the Installation Instructions). +Install Go (see the Installation Instructions).
@@ -177,7 +177,7 @@
Callers of this function can now check the second parameter; if it is
nil then it has successfully loaded a Page. If not, it will be an
error that can be handled by the caller (see the
-language specification for details).
+language specification for details).
@@ -842,7 +842,7 @@
Catching the error condition in each handler introduces a lot of repeated code. What if we could wrap each of the handlers in a function that does this validation and error checking? Go's -function +function literals provide a powerful means of abstracting functionality that can help us here.
diff --git a/doc/articles/wiki/wiki.html b/doc/articles/wiki/wiki.html index 284d6d701f7c47c27832f8dbcd37796969e9fc8f..10e1e4fe492783c43ff5ec60db5aded151859bd4 100644 --- a/doc/articles/wiki/wiki.html +++ b/doc/articles/wiki/wiki.html @@ -32,7 +32,7 @@ We will use$ to represent the command prompt.
-Install Go (see the Installation Instructions). +Install Go (see the Installation Instructions).
@@ -160,7 +160,7 @@
Callers of this function can now check the second parameter; if it is
nil then it has successfully loaded a Page. If not, it will be an
error that can be handled by the caller (see the
-language specification for details).
+language specification for details).
@@ -655,7 +655,7 @@
Catching the error condition in each handler introduces a lot of repeated code. What if we could wrap each of the handlers in a function that does this validation and error checking? Go's -function +function literals provide a powerful means of abstracting functionality that can help us here.
diff --git a/doc/contribute.html b/doc/contribute.html index 5af9af48e5e0eb7254d4e0f43e4ca532cfe24ece..73233c5880f1acf5263acf81ccfd0adeffe4c197 100644 --- a/doc/contribute.html +++ b/doc/contribute.html @@ -7,7 +7,7 @@
This document explains how to contribute changes to the Go project.
It assumes you have installed Go using the
-installation instructions and
+installation instructions and
have written and tested your code.
(Note that the gccgo frontend lives elsewhere;
see Contributing to gccgo.)
diff --git a/doc/docs.html b/doc/docs.html
index 449e233ad19e9fa6f4f6db956a410a8ec6d22e57..a820e35cb724269a59f8d99ffc6058aaeb4e1a18 100644
--- a/doc/docs.html
+++ b/doc/docs.html
@@ -20,6 +20,15 @@
+Instructions for downloading and installing the Go compilers, tools, and +libraries. +
+ ++How to use the go command to fetch, build, and install +packages, commands, and run tests. +
+A document that gives tips for writing clear, idiomatic Go code. A must read for any new Go programmer. It augments the tour and the language specification, both of which should be read first. -
- --How to write a new package and how to test code.
Answers to common questions about Go.
-A wiki full of useful information maintained by the Go community.
-The official blog of the Go project, featuring news and in-depth articles by +the Go team and guests.
@@ -72,6 +82,7 @@
+The talks marked with a red asterisk (*) were written +before Go 1 and contain some examples that are no longer correct, but they are +still of value. +
+ +A talk by Rob Pike and Andrew Gerrand presented at Google I/O 2011. It walks through the construction and deployment of a simple web application @@ -114,7 +131,7 @@ and unveils the Go runtime for App Engine. See the presentation slides.
-A talk by Andrew Gerrand presented at Google I/O Bootcamp 2011. It gives a broad overview of Go's type system and concurrency model @@ -122,7 +139,14 @@ and provides four examples of Go programs that solve real problems. See the presentation slides.
-+A talk by Andrew Gerrand presented at Google Developer Day Japan 2011. +It discusses the development of a web application that runs on Google +App Engine and renders images that it stores on Google Cloud Storage. +
+ +A presentation delivered by Rob Pike and Russ Cox at Google I/O 2010. It illustrates how programming in Go differs from other languages through a set of @@ -130,7 +154,7 @@ examples demonstrating features particular to Go. These include concurrency, embedded types, methods on any type, and program construction using interfaces.
-This talk presents the development of a complete web application in Go. It looks at design, storage, concurrency, and scaling issues in detail, using @@ -138,118 +162,38 @@ the simple example of an URL shortening service. See the presentation slides.
--An hour-long talk delivered by Rob Pike at Google in October 2009. -The language's first public introduction. (See the slides in PDF format.) The language has changed since it was made, -but it's still a good introduction. -
- --A discussion of the qualities that make Go an expressive and comprehensible -language. The talk was presented by Rob Pike at JAOO 2010. -The recording of the event was lost due to a hardware error. -
- --A tour, with some background, of the major features of Go, intended for -an audience new to the language. The talk was presented at OSCON 2010. -See the presentation slides. -
--This talk was also delivered at Sydney University in September 2010. A video -of the lecture is available -here. -
- --Rob Pike's Emerging Languages Conference presentation delivered in July 2010. See the presentation slides. Abstract: +See the GoTalks +page at the Go Wiki for +more Go talks.
--Go’s approach to concurrency differs from that of many languages, even those -(such as Erlang) that make concurrency central, yet it has deep roots. The path -from Hoare’s 1978 paper to Go provides insight into how and why Go works as it -does. -
--A description of the Go language frontend for gcc. -Ian Lance Taylor's paper delivered at the GCC Summit 2010. -
+-A short promotional video featuring Russ Cox demonstrating Go's fast compiler. +See the NonEnglish page +at the Go Wiki for localized +documentation.
-The golang-nuts mailing list is for general Go discussion.
-A list of the most popular goinstall'd -Go libraries.
+A list of external Go projects including programs and libraries.
-A list of external Go projects including programs and libraries.
+A wiki full of useful information maintained by the Go community.
#go-nuts on irc.freenode.net is the official Go IRC channel.
+The Go project's Google+ page.
+The Go project's official Twitter account.
- -These are some notes on contributing to the gccgo frontend for GCC. For information on contributing to parts of Go other than gccgo, -see Contributing to the Go project. For +see Contributing to the Go project. For information on building gccgo for yourself, -see Setting up and using gccgo. +see Setting up and using gccgo.
-You must follow the Go copyright
+You must follow the Go copyright
rules for all changes to the gccgo frontend and the associated
libgo library. Code that is part of GCC rather than gccgo must follow
the general GCC
diff --git a/doc/gccgo_install.html b/doc/gccgo_install.html
index d5fff7bf9ec9642f63b8a0d44ac66f28344440b0..ae359437a6e8262f58952d01a177639c15cb5389 100644
--- a/doc/gccgo_install.html
+++ b/doc/gccgo_install.html
@@ -1,6 +1,6 @@
@@ -15,7 +15,7 @@
Note that
Note that although
Most users don't need to do this, and will instead install
from precompiled binary packages as described in
-Getting Started,
+Getting Started,
a much simpler process.
If you want to help develop what goes into those precompiled
packages, though, read on.
@@ -29,7 +29,7 @@ This document focuses on the
diff --git a/doc/install.html b/doc/install.html
index 217b52a0e65052707ff0a75f1c08e228ba104677..4f2bb1c994a6a2b3e05a144156583845fea8de42 100644
--- a/doc/install.html
+++ b/doc/install.html
@@ -1,6 +1,6 @@
gccgo is not the 6g compiler; see
-the Installing Go instructions for that
+the Installing Go instructions for that
compiler.
gcc.gnu.org is the most convenient way
to get the source code for the compiler, that is not where the master
sources live. If you want to contribute changes to the gccgo
-compiler, see Contributing to
+compiler, see Contributing to
gccgo.
Introduction
@@ -15,7 +15,7 @@
gc Go
compiler and tools (6g, 8g etc.).
For information on how to work on gccgo, a more traditional
compiler using the GCC back end, see
-Setting up and using gccgo.
+Setting up and using gccgo.
Introduction
@@ -19,9 +19,9 @@
For information about installing the gc compiler from source, see
-Installing Go from source.
+Installing Go from source.
For information about installing gccgo, see
-Setting up and using gccgo.
+Setting up and using gccgo.
If a binary distribution is not available for your OS/arch combination you may want to try -installing from source or -installing gccgo instead of gc. +installing from source or +installing gccgo instead of gc.