Update prebuilts to go1.9rc1 ab/4215840
Test: m -j blueprint_tools
Change-Id: I8ce0d15553d871a3e79dc5836260651c0e515b5c
diff --git a/doc/articles/wiki/test.bash b/doc/articles/wiki/test.bash
index 8bbb734..cec51fd 100755
--- a/doc/articles/wiki/test.bash
+++ b/doc/articles/wiki/test.bash
@@ -20,7 +20,7 @@
rm -f get.bin final-test.bin a.out
# If called with -all, check that all code snippets compile.
-if [ "$1" == "-all" ]; then
+if [ "$1" = "-all" ]; then
for fn in *.go; do
go build -o a.out $fn
done
diff --git a/doc/cmd.html b/doc/cmd.html
index 992f176..c590f4d 100644
--- a/doc/cmd.html
+++ b/doc/cmd.html
@@ -22,7 +22,7 @@
This style of invocation allows, for instance, checking a single source file
rather than an entire package: <code>go tool vet myprogram.go</code> as
compared to <code>go vet mypackage</code>.
-Some of the commands, such as <code>yacc</code>, are accessible only through
+Some of the commands, such as <code>pprof</code>, are accessible only through
the go <code>tool</code> subcommand.
</p>
@@ -62,7 +62,7 @@
</tr>
<tr>
-<td><a href="//godoc.org/golang.org/x/tools/cmd/cover/">cover</a></td>
+<td><a href="/cmd/cover/">cover</a></td>
<td> </td>
<td>Cover is a program for creating and analyzing the coverage profiles
generated by <code>"go test -coverprofile"</code>.</td>
@@ -95,12 +95,6 @@
calls whose arguments do not align with the format string.</td>
</tr>
-<tr>
-<td><a href="/cmd/yacc/">yacc</a></td>
-<td> </td>
-<td>Yacc is a version of yacc that generates parsers implemented in Go.</td>
-</tr>
-
</table>
<p>
diff --git a/doc/code.html b/doc/code.html
index 796431a..f22e6b4 100644
--- a/doc/code.html
+++ b/doc/code.html
@@ -124,8 +124,12 @@
so <code>$HOME/go</code> on Unix,
<code>$home/go</code> on Plan 9,
and <code>%USERPROFILE%\go</code> (usually <code>C:\Users\YourName\go</code>) on Windows.
-If you would like to work in a different location, you will need to set
-<code>GOPATH</code> to the path to that directory.
+</p>
+
+<p>
+If you would like to work in a different location, you will need to
+<a href="https://golang.org/wiki/SettingGOPATH">set <code>GOPATH</code></a>
+to the path to that directory.
(Another common setup is to set <code>GOPATH=$HOME</code>.)
Note that <code>GOPATH</code> must <b>not</b> be the
same path as your Go installation.
@@ -266,7 +270,7 @@
binary. It then installs that binary to the workspace's <code>bin</code>
directory as <code>hello</code> (or, under Windows, <code>hello.exe</code>).
In our example, that will be <code>$GOPATH/bin/hello</code>, which is
-<code>$HOME/work/bin/hello</code>.
+<code>$HOME/go/bin/hello</code>.
</p>
<p>
diff --git a/doc/contrib.html b/doc/contrib.html
index 7bf3d89..fd548d7 100644
--- a/doc/contrib.html
+++ b/doc/contrib.html
@@ -34,6 +34,7 @@
<p>A <a href="/doc/devel/release.html">summary</a> of the changes between Go releases. Notes for the major releases:</p>
<ul>
+ <li><a href="/doc/go1.8">Go 1.8</a> <small>(February 2017)</small></li>
<li><a href="/doc/go1.7">Go 1.7</a> <small>(August 2016)</small></li>
<li><a href="/doc/go1.6">Go 1.6</a> <small>(February 2016)</small></li>
<li><a href="/doc/go1.5">Go 1.5</a> <small>(August 2015)</small></li>
diff --git a/doc/contribute.html b/doc/contribute.html
index f1a5b27..f204b06 100644
--- a/doc/contribute.html
+++ b/doc/contribute.html
@@ -1,14 +1,12 @@
<!--{
- "Title": "Contribution Guidelines"
+ "Title": "Contribution Guide"
}-->
-<h2 id="Introduction">Introduction</h2>
-
<p>
-This document explains how to contribute changes to the Go project.
-It assumes you have followed the
-<a href="/doc/install/source">installation instructions</a> and
-have <a href="code.html">written and tested your code</a>.
+The Go project welcomes all contributors. The process of contributing
+to the Go project may be different than many projects you are used to.
+This document is intended as a guide to help you through the contribution
+process. This guide assumes you have a basic understanding of Git and Go.
</p>
<p>
@@ -20,103 +18,73 @@
Sensitive security-related issues should be reported to <a href="mailto:security@golang.org">security@golang.org</a>.
</p>
-<h2 id="Design">Discuss your design</h2>
+<h1 id="contributor">Becoming a contributor</h1>
<p>
-The project welcomes submissions but please let everyone know what
-you're working on if you want to change or add to the Go repositories.
+Before you can contribute to the Go project you need to setup a few prerequisites.
+The Go project uses <a href="https://www.gerritcodereview.com/">Gerrit</a>, an open
+source online tool, to perform all code reviews.
+Gerrit uses your email address as a unique identifier.
+The Go project contributing flow is currently configured to work only with Google Accounts.
+You must go through the following process <em>prior to contributing</em>.
+You only need to do this once per Google Account.
</p>
+<h2 id="go-contrib-init">Automatically set up & diagnose your development environment</h3>
<p>
-Before undertaking to write something new for the Go project,
-please <a href="https://golang.org/issue/new">file an issue</a>
-(or claim an <a href="https://golang.org/issues">existing issue</a>).
-Significant changes must go through the
-<a href="https://golang.org/s/proposal-process">change proposal process</a>
-before they can be accepted.
-</p>
-
-<p>
-This process gives everyone a chance to validate the design,
-helps prevent duplication of effort,
-and ensures that the idea fits inside the goals for the language and tools.
-It also checks that the design is sound before code is written;
-the code review tool is not the place for high-level discussions.
-</p>
-
-<p>
-When planning work, please note that the Go project follows a
-<a href="https://golang.org/wiki/Go-Release-Cycle">six-month
-development cycle</a>. The latter half of each cycle is a three-month
-feature freeze during which only bug fixes and doc updates are accepted.
-New work cannot be submitted during a feature freeze.
-</p>
-
-<h2 id="Testing">Testing redux</h2>
-
-<p>
-You've <a href="code.html">written and tested your code</a>, but
-before sending code out for review, run all the tests for the whole
-tree to make sure the changes don't break other packages or programs:
+ The <code>go-contrib-init</code> tool configures and debugs your Go
+ development environment, automatically performing many of the steps
+ on this page, or telling you what you need to do next. If you wish
+ to use it, run:
</p>
<pre>
-$ cd go/src
-$ ./all.bash
+$ go get -u golang.org/x/tools/cmd/go-contrib-init
+$ cd /code/to/edit
+$ go-contrib-init
</pre>
<p>
-(To build under Windows use <code>all.bat</code>.)
+ The tool will either set things up, tell you that everything is
+ configured, or tell you what steps you need to do manually.
+</p>
+
+<h2 id="auth">Configure Git to use Gerrit</h2>
+<p>
+You'll need a web browser and a command line terminal.
+You should already have Git installed.
</p>
<p>
-After running for a while, the command should print
-"<code>ALL</code> <code>TESTS</code> <code>PASSED</code>".
-</p>
-
-<h2 id="Code_review">Code review</h2>
-
-<p>
-Changes to Go must be reviewed before they are accepted,
-no matter who makes the change.
-A custom git command called <code>git-codereview</code>,
-discussed below, helps manage the code review process through a Google-hosted
-<a href="https://go-review.googlesource.com/">instance</a> of the code review
-system called <a href="https://www.gerritcodereview.com/">Gerrit</a>.
-</p>
-
-<h3 id="auth">Set up authentication for code review</h3>
-
-<p>
-Gerrit uses Google Accounts for authentication. If you don't have
-a Google Account, you can create an account which
+Gerrit uses Google Accounts for authentication.
+If you don't have a Google Account, you can create an account which
<a href="https://www.google.com/accounts/NewAccount">includes
a new Gmail email account</a> or create an account associated
<a href="https://accounts.google.com/SignUpWithoutGmail">with your existing
email address</a>.
</p>
-<p>
-The email address associated with the Google Account you use will be recorded in
-the <a href="https://go.googlesource.com/go/+log/">change log</a>
-and in the <a href="/CONTRIBUTORS">contributors file</a>.
-</p>
+<h3>Step 1: Sign in to googlesource and generate a password</h3>
<p>
-To set up your account in Gerrit, visit
-<a href="https://go.googlesource.com">go.googlesource.com</a>
+Visit <a href="https://go.googlesource.com">go.googlesource.com</a>
and click on "Generate Password" in the page's top right menu bar.
-</p>
-
-<p>
You will be redirected to accounts.google.com to sign in.
</p>
+<h3>Step 2: Run the provided script</h3>
<p>
-Once signed in, you are returned back to go.googlesource.com to "Configure Git".
-Follow the instructions on the page.
-(If you are on a Windows computer, you should instead follow the instructions
-in the yellow box to run the command.)
+After signing in, you are taken to a page on go.googlesource.com with the title "Configure Git".
+This page contains a personalized script which when run locally will configure git
+to have your unique authentication key.
+This key is paired with one generated server side similar to how ssh keys work.
+</p>
+
+<p>
+Copy and run this script locally in your command line terminal.
+(On a Windows computer using cmd you should instead follow the instructions
+in the yellow box to run the command. If you are using git-bash use the same
+script as *nix.)
</p>
<p>
@@ -124,23 +92,25 @@
and Git is configured to use this file.
</p>
-<h3 id="gerrit">Register with Gerrit</h3>
+<h3 id="gerrit">Step 3: Register with Gerrit</h3>
<p>
-Now that you have your authentication token,
-you need to register your account with Gerrit.
-To do this, visit
-<a href="https://go-review.googlesource.com/login/">
-go-review.googlesource.com/login/</a>. You will immediately be redirected
-to Google Accounts. Sign in using the same Google Account you used above.
-That is all that is required.
+Now that you have your authentication token, you need to register your
+account with Gerrit.
+To do this, visit <a href="https://go-review.googlesource.com/login/">
+go-review.googlesource.com/login/</a>.
+Sign in using the same Google Account you used above.
</p>
-<h3 id="cla">Contributor License Agreement</h3>
+<h2 id="cla">Contributor License Agreement</h2>
-<p>Gerrit serves as the gatekeeper and uses your e-mail address as the key.
-To send your first change to the Go project from a given address,
-you must have completed one of the contributor license agreements:
+<h3 id="which_cla">Which CLA</h3>
+<p>
+Before sending your first change to the Go project
+you must have completed one of the following two CLAs.
+Which CLA you should sign depends on who owns the copyright to your work.
+</p>
+
<ul>
<li>
If you are the copyright holder, you will need to agree to the
@@ -151,37 +121,49 @@
If your organization is the copyright holder, the organization
will need to agree to the
<a href="https://developers.google.com/open-source/cla/corporate">corporate
-contributor license agreement</a>.
-(If the copyright holder for your code has already completed the
-agreement in connection with another Google open source project,
-it does not need to be completed again.)
+contributor license agreement</a>.<br>
</li>
</ul>
<p>
-You can use the links above to create and sign the contributor license agreement
-or you can show your current agreements and create new ones through the Gerrit
-interface. <a href="https://go-review.googlesource.com/login/">Log into Gerrit</a>,
-click your name in the upper-right, choose "Settings", then select "Agreements"
-from the topics on the left. If you do not have a signed agreement listed here,
-you can create one by clicking "New Contributor Agreement" and following the steps.
+<i>If the copyright holder for your contribution has already completed the
+agreement in connection with another Google open source project,
+it does not need to be completed again.</i>
+</p>
+
+<h3 id="signing_cla">Completing the CLA</h3>
+
+<p>
+You can see your currently signed agreements and sign new ones through the Gerrit
+interface.
+To do this, <a href="https://go-review.googlesource.com/login/">Log into Gerrit</a>,
+then visit the <a href="https://go-review.googlesource.com/settings/agreements">Agreements</a>
+page.
+If you do not have a signed agreement listed there, you can create one
+by clicking "New Contributor Agreement" and following the steps.
</p>
<p>
-This rigmarole only needs to be done for your first submission for each email address.
+If the copyright holder for the code you are submitting changes — for example,
+if you start contributing code on behalf of a new company — please send email
+to golang-dev and let us know, so that we can make sure an appropriate agreement is
+completed and update the <code>AUTHORS</code> file.
</p>
+<span id="Code_review"></span>
+<h1 id="prepare_dev_env">Preparing a Development Environment for Contributing</h1>
+
+<h2 id="git-codereview">Setting up Git for submission to Gerrit</h2>
<p>
-If the copyright holder for the code you are submitting changes—for example,
-if you start contributing code on behalf of a new company—please send email
-to let us know, so that we can make sure an appropriate agreement is completed
-and update the <code>AUTHORS</code> file.
+Changes to Go must be reviewed before they are accepted, no matter who makes the change.
+A custom git command called <code>git-codereview</code>, discussed below,
+helps manage the code review process through a Google-hosted
+<a href="https://go-review.googlesource.com/">instance</a> Gerrit.
</p>
-<h3 id="git-codereview">Install the git-codereview command</h3>
-
+<h3 id="git-codereview_install">Install the git-codereview command</h3>
<p>
-Now install the <code>git-codereview</code> command by running,
+Install the <code>git-codereview</code> command by running,
</p>
<pre>
@@ -202,18 +184,28 @@
</p>
<p>
-<b>Note to Git aficionados:</b>
-The <code>git-codereview</code> command is not required to
-upload and manage Gerrit code reviews. For those who prefer plain Git, the text
-below gives the Git equivalent of each git-codereview command.
+On Windows, when using git-bash you must make sure that
+<code>git-codereview.exe</code> is in your git exec-path.
+Run <code>git --exec-path</code> to discover the right location then create a
+symbolic link or simply copy the executible from $GOPATH/bin to this directory.
</p>
-<p>If you do use plain
-Git, note that you still need the commit hooks that the git-codereview command
-configures; those hooks add a Gerrit <code>Change-Id</code> line to the commit
-message and check that all Go source files have been formatted with gofmt. Even
-if you intend to use plain Git for daily work, install the hooks in a new Git
-checkout by running <code>git-codereview</code> <code>hooks</code>.
+<p>
+<b>Note to Git aficionados:</b>
+The <code>git-codereview</code> command is not required to
+upload and manage Gerrit code reviews.
+For those who prefer plain Git, the text below gives the Git equivalent of
+each git-codereview command.
+</p>
+
+<p>
+If you do use plain Git, note that you still need the commit hooks that the
+git-codereview command configures; those hooks add a Gerrit
+<code>Change-Id</code> line to the commit message and check that all Go source
+files have been formatted with gofmt.
+Even if you intend to use plain Git for
+daily work, install the hooks in a new Git checkout by running
+<code>git-codereview</code> <code>hooks</code>.
</p>
<p>
@@ -264,7 +256,8 @@
sync = codereview sync
</pre>
-<h3 id="help">Understanding the git-codereview command</h3>
+<span id="help"></span>
+<h3 id="understanding_git-codereview">Understanding the git-codereview command</h3>
<p>After installing the <code>git-codereview</code> command, you can run</p>
@@ -277,11 +270,70 @@
You can also read the <a href="https://godoc.org/golang.org/x/review/git-codereview">command documentation</a>.
</p>
-<h3 id="master">Switch to the master branch</h3>
+
+<h1 id="making_a_contribution">Making a Contribution</h1>
+
+<h2 id="Design">Discuss your design</h2>
+
+<p>
+The project welcomes submissions but please let everyone know what
+you're working on if you want to change or add to the Go repositories.
+</p>
+
+<p>
+Before undertaking to write something new for the Go project,
+please <a href="https://golang.org/issue/new">file an issue</a>
+(or claim an <a href="https://golang.org/issues">existing issue</a>).
+Significant changes must go through the
+<a href="https://golang.org/s/proposal-process">change proposal process</a>
+before they can be accepted.
+</p>
+
+<p>
+This process gives everyone a chance to validate the design,
+helps prevent duplication of effort,
+and ensures that the idea fits inside the goals for the language and tools.
+It also checks that the design is sound before code is written;
+the code review tool is not the place for high-level discussions.
+</p>
+
+<p>
+When planning work, please note that the Go project follows a <a
+href="https://golang.org/wiki/Go-Release-Cycle">six-month development cycle</a>.
+The latter half of each cycle is a three-month feature freeze during
+which only bug fixes and doc updates are accepted. New contributions can be
+sent during a feature freeze but will not be accepted until the freeze thaws.
+</p>
+
+<h2 id="making_a_change">Making a change</h2>
+
+<h3 id="checkout_go">Getting Go Source</h3>
+<p>
+First you need to have a local copy of the source checked out from the correct
+repository.
+As Go builds Go you will also likely need to have a working version
+of Go installed (some documentation changes may not need this).
+This should be a recent version of Go and can be obtained via any package or
+binary distribution or you can build it from source.
+</p>
+
+<p>
+You should checkout the Go source repo anywhere you want as long as it's
+outside of your $GOPATH.
+Go to a directory where you want the source to appear and run the following
+command in a terminal.
+</p>
+
+<pre>
+$ git clone https://go.googlesource.com/go
+$ cd go
+</pre>
+
+<h3 id="master">Contributing to the main Go tree</h3>
<p>
Most Go installations use a release branch, but new changes should
-only be made based on the master branch.
+only be made based on the master branch. <br>
(They may be applied later to a release branch as part of the release process,
but most contributors won't do this themselves.)
Before making a change, make sure you start on the master branch:
@@ -297,10 +349,61 @@
<code>git</code> <code>pull</code> <code>-r</code>.)
</p>
-<h3 id="change">Make a change</h3>
+<h3 id="subrepos">Contributing to subrepositories (golang.org/x/...)</h3>
<p>
-The entire checked-out tree is writable.
+If you are contributing a change to a subrepository, obtain the
+Go package using <code>go get</code>. For example, to contribute
+to <code>golang.org/x/oauth2</code>, check out the code by running:
+</p>
+
+<pre>
+$ go get -d golang.org/x/oauth2/...
+</pre>
+
+<p>
+Then, change your directory to the package's source directory
+(<code>$GOPATH/src/golang.org/x/oauth2</code>).
+</p>
+
+<h3 id="change">Make your changes</h3>
+
+<p>
+The entire checked-out tree is editable.
+Make your changes as you see fit ensuring that you create appropriate
+tests along with your changes. Test your changes as you go.
+</p>
+
+<h3 id="copyright">Copyright</h3>
+
+<p>
+Files in the Go repository don't list author names, both to avoid clutter
+and to avoid having to keep the lists up to date.
+Instead, your name will appear in the
+<a href="https://golang.org/change">change log</a> and in the <a
+href="/CONTRIBUTORS"><code>CONTRIBUTORS</code></a> file and perhaps the <a
+href="/AUTHORS"><code>AUTHORS</code></a> file.
+These files are automatically generated from the commit logs perodically.
+The <a href="/AUTHORS"><code>AUTHORS</code></a> file defines who “The Go
+Authors”—the copyright holders—are.
+</p>
+
+<p>New files that you contribute should use the standard copyright header:</p>
+
+<pre>
+// Copyright 2017 The Go Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style
+// license that can be found in the LICENSE file.
+</pre>
+
+<p>
+Files in the repository are copyright the year they are added.
+Do not update the copyright year on files that you change.
+</p>
+
+<h3 id="commit_changes">Commit your changes</h3>
+
+<p>
Once you have edited files, you must tell Git that they have been modified.
You must also tell Git about any files that are added, removed, or renamed files.
These operations are done with the usual Git commands,
@@ -311,16 +414,20 @@
</p>
<p>
-If you wish to checkpoint your work, or are ready to send the code out for review, run</p>
+Once you have the changes queued up, you will want to commit them.
+In the Go contribution workflow this is done with a <code>git</code>
+<code>change</code> command, which creates a local branch and commits the changes
+directly to that local branch.
+</p>
<pre>
$ git change <i><branch></i>
</pre>
<p>
-from any directory in your Go repository to commit the changes so far.
The name <i><branch></i> is an arbitrary one you choose to identify the
-local branch containing your changes.
+local branch containing your changes and will not be used elsewhere.
+This is an offline operation and nothing will be sent to the server yet.
</p>
<p>
@@ -331,9 +438,11 @@
</p>
<p>
-Git will open a change description file in your editor.
-(It uses the editor named by the <code>$EDITOR</code> environment variable,
+As the <code>git</code> <code>commit</code> is the final step, Git will open an
+editor to ask for a commit message. (It uses the editor named by
+the <code>$EDITOR</code> environment variable,
<code>vi</code> by default.)
+
The file will look like:
</p>
@@ -352,7 +461,7 @@
with a thorough description of your change.
The first line of the change description is conventionally a one-line
summary of the change, prefixed by the primary affected package,
-and is used as the subject for code review mail.
+and is used as the subject for code review email.
It should complete the sentence "This change modifies Go to _____."
The rest of the description elaborates and should provide context for the
change and explain what it does.
@@ -387,7 +496,7 @@
<p>
The commented section of the file lists all the modified files in your client.
-It is best to keep unrelated changes in different change lists,
+It is best to keep unrelated changes in different commits,
so if you see a file listed that should not be included, abort
the command and move that file to a different branch.
</p>
@@ -395,7 +504,7 @@
<p>
The special notation "Fixes #159" associates the change with issue 159 in the
<a href="https://golang.org/issue/159">Go issue tracker</a>.
-When this change is eventually submitted, the issue
+When this change is eventually applied, the issue
tracker will automatically mark the issue as fixed.
(There are several such conventions, described in detail in the
<a href="https://help.github.com/articles/closing-issues-via-commit-messages/">GitHub Issue Tracker documentation</a>.)
@@ -407,6 +516,13 @@
</p>
<p>
+You must have the $EDITOR environment variable set properly and working properly (exiting cleanly)
+for this operation to succeed.
+If you run into any issues at this step, it's likely your editor isn't exiting cleanly.
+Try setting a different editor in your $EDITOR environment variable.
+</p>
+
+<p>
If you wish to do more editing, re-stage your changes using
<code>git</code> <code>add</code>, and then run
</p>
@@ -416,8 +532,8 @@
</pre>
<p>
-to update the change description and incorporate the staged changes. The
-change description contains a <code>Change-Id</code> line near the bottom,
+to update the change description and incorporate the staged changes.
+The change description contains a <code>Change-Id</code> line near the bottom,
added by a Git commit hook during the initial
<code>git</code> <code>change</code>.
That line is used by Gerrit to match successive uploads of the same change.
@@ -429,10 +545,38 @@
runs <code>git</code> <code>commit</code> <code>--amend</code>.)
</p>
-<h3 id="mail">Mail the change for review</h3>
+<h3 id="Testing">Testing</h3>
<p>
-Once the change is ready, mail it out for review:
+You've <a href="code.html">written and tested your code</a>, but
+before sending code out for review, run all the tests for the whole
+tree to make sure the changes don't break other packages or programs:
+</p>
+
+<pre>
+$ cd go/src
+$ ./all.bash
+</pre>
+
+<p>
+(To build under Windows use <code>all.bat</code>.)
+</p>
+
+<p>
+After running for a while, the command should print
+</p>
+
+<pre>
+"ALL TESTS PASSED".
+</pre>
+
+<h3 id="mail">Send the change for review</h3>
+
+<p>
+Once the change is ready, send it for review.
+This is similar to a <code>git push</code> in a GitHub style workflow.
+This is done via the mail alias setup earlier which despite its name, doesn't
+directly mail anything, it simply sends the change to Gerrit via git push.
</p>
<pre>
@@ -440,25 +584,6 @@
</pre>
<p>
-You can specify a reviewer or CC interested parties
-using the <code>-r</code> or <code>-cc</code> options.
-Both accept a comma-separated list of email addresses:
-</p>
-
-<pre>
-$ git mail -r joe@golang.org -cc mabel@example.com,math-nuts@swtch.com
-</pre>
-
-<p>
-Unless explicitly told otherwise, such as in the discussion leading
-up to sending in the change list, it's better not to specify a reviewer.
-All changes are automatically CC'ed to the
-<a href="https://groups.google.com/group/golang-codereviews">golang-codereviews@googlegroups.com</a>
-mailing list. If this is your first ever change, there may be a moderation
-delay before it appears on the mailing list, to prevent spam.
-</p>
-
-<p>
(In Git terms, <code>git</code> <code>mail</code> pushes the local committed
changes to Gerrit using <code>git</code> <code>push</code> <code>origin</code>
<code>HEAD:refs/for/master</code>.)
@@ -466,7 +591,7 @@
<p>
If your change relates to an open issue, please add a comment to the issue
-announcing your proposed fix, including a link to your CL.
+announcing your proposed fix, including a link to your change.
</p>
<p>
@@ -479,7 +604,76 @@
remote: https://go-review.googlesource.com/99999 math: improved Sin, Cos and Tan precision for very large arguments
</pre>
-<h3 id="review">Reviewing code</h3>
+<h3>Troubleshooting</h3>
+
+<p>
+The most common way that the <code>git mail</code> command fails is because the
+email address used has not gone through the setup above.
+<br>
+If you see something like...
+</p>
+
+<pre>
+remote: Processing changes: refs: 1, done
+remote:
+remote: ERROR: In commit ab13517fa29487dcf8b0d48916c51639426c5ee9
+remote: ERROR: author email address XXXXXXXXXXXXXXXXXXX
+remote: ERROR: does not match your user account.
+</pre>
+
+<p>
+You need to either add the email address listed to the CLA or set this repo to use
+another email address already approved.
+</p>
+
+<p>
+First let's change the email address for this repo so this doesn't happen again.
+You can change your email address for this repo with the following command:
+</p>
+
+<pre>
+$ git config user.email email@address.com
+</pre>
+
+<p>
+Then change the previous commit to use this alternative email address.
+You can do that with:
+</p>
+
+<pre>
+$ git commit --amend --author="Author Name <email@address.com>"
+</pre>
+
+<p>
+Finally try to resend with:
+</p>
+
+<pre>
+$ git mail
+</pre>
+
+<h3 id="cc">Specifying a reviewer / CCing others</h3>
+
+<p>
+Unless explicitly told otherwise, such as in the discussion leading
+up to sending in the change, it's better not to specify a reviewer.
+All changes are automatically CC'ed to the
+<a href="https://groups.google.com/group/golang-codereviews">golang-codereviews@googlegroups.com</a>
+mailing list. If this is your first ever change, there may be a moderation
+delay before it appears on the mailing list, to prevent spam.
+</p>
+
+<p>
+You can specify a reviewer or CC interested parties
+using the <code>-r</code> or <code>-cc</code> options.
+Both accept a comma-separated list of email addresses:
+</p>
+
+<pre>
+$ git mail -r joe@golang.org -cc mabel@example.com,math-nuts@swtch.com
+</pre>
+
+<h2 id="review">Going through the review process</h2>
<p>
Running <code>git</code> <code>mail</code> will send an email to you and the
@@ -491,7 +685,15 @@
(Unlike with the old Rietveld review system, replying by mail has no effect.)
</p>
-<h3 id="revise">Revise and upload</h3>
+<h3 id="revise">Revise and resend</h3>
+
+<p>
+The Go contribution workflow is optimized for iterative revisions based on
+feedback.
+It is rare that an initial contribution will be ready to be applied as is.
+As you revise your contribution and resend Gerrit will retain a history of
+all the changes and comments made in the single URL.
+</p>
<p>
You must respond to review comments through the web interface.
@@ -502,7 +704,7 @@
When you have revised the code and are ready for another round of review,
stage those changes and use <code>git</code> <code>change</code> to update the
commit.
-To send the update change list for another round of review,
+To send the updated change for another round of review,
run <code>git</code> <code>mail</code> again.
</p>
@@ -534,6 +736,8 @@
<code>git</code> <code>pull</code> <code>-r</code>.)
</p>
+<h3 id="resolving_conflicts">Resolving Conflicts</h3>
+
<p>
If files you were editing have changed, Git does its best to merge the
remote changes into your local changes.
@@ -609,8 +813,8 @@
<p>
Git doesn't show it, but suppose the original text that both edits
started with was 1e8; you changed it to 1e10 and the other change to 1e9,
-so the correct answer might now be 1e10. First, edit the section
-to remove the markers and leave the correct code:
+so the correct answer might now be 1e10.
+First, edit the section to remove the markers and leave the correct code:
</p>
<pre>
@@ -639,10 +843,13 @@
<h3 id="download">Reviewing code by others</h3>
<p>
-You can import a change proposed by someone else into your local Git repository.
+As part of the review process reviewers can propose changes directly (in the
+GitHub workflow this would be someone else attaching commits to a pull request).
+
+You can import these changes proposed by someone else into your local Git repository.
On the Gerrit review page, click the "Download â–¼" link in the upper right
-corner, copy the "Checkout" command and run it from your local Git repo.
-It should look something like this:
+corner, copy the "Checkout" command and run it from your local Git repo. It
+should look something like this:
</p>
<pre>
@@ -653,11 +860,11 @@
To revert, change back to the branch you were working in.
</p>
-<h3 id="submit">Submit the change after the review</h3>
+<h2 id="submit">Apply the change to the master branch</h2>
<p>
After the code has been <code>LGTM</code>'ed, an approver may
-submit it to the master branch using the Gerrit UI.
+apply it to the master branch using the Gerrit UI.
There is a "Submit" button on the web page for the change
that appears once the change is approved (marked +2).
</p>
@@ -669,41 +876,13 @@
in the repository.
Since the method used to integrate the changes is "Cherry Pick",
the commit hashes in the repository will be changed by
-the submit operation.
+the "Submit" operation.
</p>
-<h3 id="more">More information</h3>
+<h2 id="more">More information</h2>
<p>
-In addition to the information here, the Go community maintains a <a href="https://golang.org/wiki/CodeReview">CodeReview</a> wiki page.
+In addition to the information here, the Go community maintains a <a
+href="https://golang.org/wiki/CodeReview">CodeReview</a> wiki page.
Feel free to contribute to this page as you learn the review process.
</p>
-
-<h2 id="copyright">Copyright</h2>
-
-<p>Files in the Go repository don't list author names,
-both to avoid clutter and to avoid having to keep the lists up to date.
-Instead, your name will appear in the
-<a href="https://golang.org/change">change log</a>
-and in the <a href="/CONTRIBUTORS"><code>CONTRIBUTORS</code></a> file
-and perhaps the <a href="/AUTHORS"><code>AUTHORS</code></a> file.
-</p>
-
-<p>The <a href="/CONTRIBUTORS"><code>CONTRIBUTORS</code></a> file
-defines who the Go contributors—the people—are;
-the <a href="/AUTHORS"><code>AUTHORS</code></a> file defines
-who “The Go Authors”—the copyright holders—are.
-These files will be periodically updated based on the commit logs.
-
-<p>Code that you contribute should use the standard copyright header:</p>
-
-<pre>
-// Copyright 2017 The Go Authors. All rights reserved.
-// Use of this source code is governed by a BSD-style
-// license that can be found in the LICENSE file.
-</pre>
-
-<p>
-Files in the repository are copyright the year they are added. It is not
-necessary to update the copyright year on files that you change.
-</p>
diff --git a/doc/devel/release.html b/doc/devel/release.html
index d046149..e4821ff 100644
--- a/doc/devel/release.html
+++ b/doc/devel/release.html
@@ -15,19 +15,12 @@
<h2 id="policy">Release Policy</h2>
<p>
-Each major Go release obsoletes and ends support for the previous one.
-For example, if Go 1.5 has been released, then it is the current release
-and Go 1.4 and earlier are no longer supported.
-We fix critical problems in the current release as needed by issuing minor revisions
-(for example, Go 1.5.1, Go 1.5.2, and so on).
-</p>
-
-<p>
-As a special case, we issue minor revisions for critical security problems
-in both the current release and the previous release.
-For example, if Go 1.5 is the current release then we will issue minor revisions
-to fix critical security problems in both Go 1.4 and Go 1.5 as they arise.
-See the <a href="/security">security policy</a> for more details.
+Each major Go release is supported until there are two newer major releases.
+For example, Go 1.8 is supported until Go 1.10 is released,
+and Go 1.9 is supported until Go 1.11 is released.
+We fix critical problems, including <a href="/security">critical security problems</a>,
+in supported releases as needed by issuing minor revisions
+(for example, Go 1.8.1, Go 1.8.2, and so on).
</p>
<h2 id="go1.8">go1.8 (released 2017/02/16)</h2>
@@ -37,6 +30,32 @@
Read the <a href="/doc/go1.8">Go 1.8 Release Notes</a> for more information.
</p>
+<h3 id="go1.8.minor">Minor revisions</h3>
+
+<p>
+go1.8.1 (released 2017/04/07) includes fixes to the compiler, linker, runtime,
+documentation, <code>go</code> command and the <code>crypto/tls</code>,
+<code>encoding/xml</code>, <code>image/png</code>, <code>net</code>,
+<code>net/http</code>, <code>reflect</code>, <code>text/template</code>,
+and <code>time</code> packages.
+See the <a href="https://github.com/golang/go/issues?q=milestone%3AGo1.8.1">Go
+1.8.1 milestone</a> on our issue tracker for details.
+</p>
+
+<p>
+go1.8.2 (released 2017/05/23) includes a security fix to the
+<code>crypto/elliptic</code> package.
+See the <a href="https://github.com/golang/go/issues?q=milestone%3AGo1.8.2">Go
+1.8.2 milestone</a> on our issue tracker for details.
+</p>
+
+<p>
+go1.8.3 (released 2017/05/24) includes fixes to the compiler, runtime,
+documentation, and the <code>database/sql</code> package.
+See the <a href="https://github.com/golang/go/issues?q=milestone%3AGo1.8.3">Go
+1.8.3 milestone</a> on our issue tracker for details.
+</p>
+
<h2 id="go1.7">go1.7 (released 2016/08/15)</h2>
<p>
@@ -83,6 +102,13 @@
1.7.5 milestone</a> on our issue tracker for details.
</p>
+<p>
+go1.7.6 (released 2017/05/23) includes the same security fix as Go 1.8.2 and
+was released at the same time.
+See the <a href="https://github.com/golang/go/issues?q=milestone%3AGo1.8.2">Go
+1.8.2 milestone</a> on our issue tracker for details.
+</p>
+
<h2 id="go1.6">go1.6 (released 2016/02/17)</h2>
<p>
diff --git a/doc/docs.html b/doc/docs.html
index 1ccd1f3..92392e2 100644
--- a/doc/docs.html
+++ b/doc/docs.html
@@ -57,6 +57,12 @@
install packages, commands, and run tests.
</p>
+<h3 id="editors"><a href="editors.html">Editor plugins and IDEs</a></h3>
+<p>
+A document that summarizes commonly used editor plugins and IDEs with
+Go support.
+</p>
+
<h3 id="effective_go"><a href="effective_go.html">Effective Go</a></h3>
<p>
A document that gives tips for writing clear, idiomatic Go code.
diff --git a/doc/editors.html b/doc/editors.html
new file mode 100644
index 0000000..1448781
--- /dev/null
+++ b/doc/editors.html
@@ -0,0 +1,210 @@
+<!--{
+ "Title": "Editor plugins and IDEs",
+ "Template": true
+}-->
+
+<h2 id="introduction">Introduction</h2>
+
+<p>
+ This document lists commonly used editor plugins and IDEs from the Go ecosystem
+ that make Go development more productive and seamless.
+ A comprehensive list of editor support and IDEs for Go development is available at
+ <a href="http://golang.org/wiki/IDEsAndTextEditorPlugins">the wiki</a>.
+</p>
+
+<h2 id="options">Options</h2>
+<p>
+The Go ecosystem provides a variety of editor plugins and IDEs to enhance your day-to-day
+editing, navigation, testing, and debugging experience.
+</p>
+
+<ul>
+<li><a href="https://github.com/fatih/vim-go">Vim Go</a>: a plugin for Vim to provide Go programming language support</li>
+<li><a href="https://marketplace.visualstudio.com/items?itemName=lukehoban.Go">Visual Studio Code Go</a>:
+an extension for Visual Studio Code to provide support for the Go programming language</li>
+<li><a href="https://www.jetbrains.com/go">Gogland</a>: Gogland is distributed either as a standalone IDE
+or as a plugin for the IntelliJ Platform IDEs</li>
+</ul>
+
+<p>
+Note that these are only a few top solutions; a more comphensive
+community-maintained list of
+<a href="https://github.com/golang/go/wiki/IDEsAndTextEditorPlugins">IDEs and text editor plugins</a>
+is available at the Wiki.
+</p>
+
+<p>
+Each development environment integrates a number of Go-specific tools.
+The following feature matrix lists and compares the most significant features.
+</p>
+
+<table class="features-matrix">
+ <tr>
+ <th></th>
+ <th><img title="Vim Go" src="/doc/editors/vimgo.png"><br>Vim Go</th>
+ <th><img title="Visual Studio Code" src="/doc/editors/vscodego.png"><br>Visual Studio Code Go</th>
+ <th><img title="Gogland" src="/doc/editors/gogland.png"><br>Gogland</th>
+ </tr>
+ <tr>
+ <td class="feature-row" colspan="4">Editing features</td>
+ </tr>
+ <tr>
+ <td>Build and run from the editor/IDE</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr>
+ <td>Autocompletion of identifers (variable, method, and function names)</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr>
+ <td>Autocompletion based on type</td>
+ <td class="no">No</td>
+ <td class="no">No</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr>
+ <td>Rename identifiers</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr>
+ <td>Auto format, build, vet, and lint on save</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes<sup>1</sup></td>
+ </tr>
+ <tr>
+ <td>Auto insert import paths and remove unused on save</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes<sup>2</sup></td>
+ </tr>
+ <tr>
+ <td>Auto generate JSON, XML tags for struct fields</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr>
+ <td class="feature-row" colspan="4">Navigation features</td>
+ </tr>
+ <tr>
+ <td>Display documentation inline, or open godoc in browser</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr>
+ <td>Switch between <code>*.go</code> and <code>*_test.go</code> file</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr>
+ <td>Jump to definition and referees</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr>
+ <td>Look up for interface implementations</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr>
+ <td>Search for callers and callees</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr>
+ <td class="feature-row" colspan="4">Testing and debugging features</td>
+ </tr>
+ <tr>
+ <td>Debugger support</td>
+ <td class="no">No</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr>
+ <td>Run a single test case, all tests from file, or all tests from a package</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr>
+ <td>Auto generate tests for packages, files and identifiers</td>
+ <td class="no">No</td>
+ <td class="yes">Yes</td>
+ <td class="no">No</td>
+ </tr>
+ <tr>
+ <td>Debug tests</td>
+ <td class="no">No</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr>
+ <td>Display test coverage</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ <td class="yes">Yes</td>
+ </tr>
+ <tr class="download">
+ <td></td>
+ <td><a href="https://github.com/fatih/vim-go">Install<a/></td>
+ <td><a href="https://marketplace.visualstudio.com/items?itemName=lukehoban.Go">Install<a/></td>
+ <td><a href="https://www.jetbrains.com/go">Install<a/></td>
+ </tr>
+</table>
+
+<p>
+<sup>1</sup>: Possible when enabled via Settings > Go > On Save, <code>go</code> <code>vet</code> and <code>golint</code> are available via plugins. Also runs tests on save if configured.
+<br>
+<sup>2</sup>: Additionally, user input can disambiguate when two or more options are available.
+</p>
+
+</div>
+
+<style>
+.features-matrix {
+ min-width: 800px;
+ border-collapse: collapse;
+}
+.features-matrix th {
+ width: 60px;
+ text-align: center;
+ font-size: 14px;
+ color: #666;
+}
+.features-matrix th img {
+ width: 48px;
+}
+.features-matrix .yes {
+ text-align: center;
+}
+.features-matrix .no {
+ text-align: center;
+ background-color: #ffe9e9;
+}
+.features-matrix .download {
+ font-weight: bold;
+ text-align: center;
+}
+.features-matrix td {
+ padding: 11px 5px 11px 5px;
+ border-bottom: solid 1px #ebebeb;
+}
+.features-matrix .feature-row {
+ background-color: #ebebeb;
+ font-weight: bold;
+}
+</style>
+
+<!--TODO(jbd): Add the Atom comparison-->
\ No newline at end of file
diff --git a/doc/editors/gogland.png b/doc/editors/gogland.png
new file mode 100644
index 0000000..842f089
--- /dev/null
+++ b/doc/editors/gogland.png
Binary files differ
diff --git a/doc/editors/vimgo.png b/doc/editors/vimgo.png
new file mode 100644
index 0000000..cf317ef
--- /dev/null
+++ b/doc/editors/vimgo.png
Binary files differ
diff --git a/doc/editors/vscodego.png b/doc/editors/vscodego.png
new file mode 100644
index 0000000..4e6c7b8
--- /dev/null
+++ b/doc/editors/vscodego.png
Binary files differ
diff --git a/doc/effective_go.html b/doc/effective_go.html
index e3f3124..bc70b0c 100644
--- a/doc/effective_go.html
+++ b/doc/effective_go.html
@@ -1580,7 +1580,7 @@
<p>
Sometimes you need to distinguish a missing entry from
a zero value. Is there an entry for <code>"UTC"</code>
-or is that the empty string because it's not in the map at all?
+or is that 0 because it's not in the map at all?
You can discriminate with a form of multiple assignment.
</p>
<pre>
@@ -1833,7 +1833,7 @@
</p>
<pre>
func Min(a ...int) int {
- min := int(^uint(0) >> 1) // largest int
+ min := int(^uint(0) >> 1) // largest int
for _, i := range a {
if i < min {
min = i
diff --git a/doc/go1.8.html b/doc/go1.8.html
index cf4c669..611f5ee 100644
--- a/doc/go1.8.html
+++ b/doc/go1.8.html
@@ -1304,7 +1304,7 @@
request must have the new
<a href="/pkg/net/http/#Request"><code>Request.GetBody</code></a>
field defined.
- <a href="pkg/net/http/#NewRequest"><code>NewRequest</code></a>
+ <a href="/pkg/net/http/#NewRequest"><code>NewRequest</code></a>
sets <code>Request.GetBody</code> automatically for common
body types.
</li>
diff --git a/doc/go1.8.txt b/doc/go1.8.txt
deleted file mode 100644
index caa9a72..0000000
--- a/doc/go1.8.txt
+++ /dev/null
@@ -1,55 +0,0 @@
-This file lists things yet to be moved into go1.8.html or deemed too
-minor to mention. Either way, delete from here when done.
-
-Tools:
-
-go: -buildmode=c-archive now builds PIC on ELF (CL 24180)
-go: mobile pkg dir change, recommend using go list in scripts (CL 24930, CL 27929)
-go, dist: can set default pkg-config tool using PKG_CONFIG env var (CL 29991)
-go: can set secure/insecure GIT schemes using GIT_ALLOW_PROTOCOL env var (CL 30135)
-
-API additions and behavior changes:
-
-cmd/compile, runtime, etc: get rid of constant FP registers (CL 28095)
-cmd/compile, runtime: add go:yeswritebarrierrec pragma (CL 30938)
-cmd/compile/internal/gc: enable new parser by default (CL 27203)
-cmd/compile/internal/syntax: fast Go syntax trees, initial commit (CL 27195)
-cmd/compile: add compiler phase timing (CL 24462)
-cmd/compile: add inline explainer (CL 22782)
-cmd/compile: enable flag-specified dump of specific phase+function (CL 23044)
-
-cmd/internal/obj, cmd/link: darwin dynlink support (CL 29393)
-cmd/internal/objfile: add ppc64/ppc64le disassembler support (CL 9682)
-cmd/link, cmd/go: delay linking of mingwex and mingw32 until very end (CL 26670)
-cmd/link: R_ADDR dynamic relocs for internal PIE (CL 29118)
-cmd/link: add trampolines for too far calls in ppc64x (CL 30850)
-cmd/link: allow internal PIE linking (CL 28543)
-cmd/link: fix -X importpath.name=value when import path needs escaping (CL 31970)
-cmd/link: fix -buildmode=pie / -linkshared combination (CL 28996)
-cmd/link: for -buildmode=exe pass -no-pie to external linker (CL 33106)
-cmd/link: insert trampolines for too-far jumps on ARM (CL 29397)
-cmd/link: non-executable stack support for Solaris (CL 24142)
-cmd/link: put text at address 0x1000000 on darwin/amd64 (CL 32185)
-cmd/link: remove the -shared flag (CL 28852)
-cmd/link: split large elf text sections on ppc64x (CL 27790)
-cmd/link: trampoline support for external linking on ARM (CL 31143)
-cmd/objdump: implement objdump of .o files (CL 24818)
-
-go/build: allow % in ${SRCDIR} expansion for Jenkins (CL 31611)
-go/build: do not record go:binary-only-package if build tags not satisfied (CL 31577)
-go/build: implement default GOPATH (CL 32019)
-
-runtime/race: update race runtime (CL 32160)
-runtime: assume 64kB physical pages on ARM (CL 25021)
-runtime: disable stack rescanning by default (CL 31766)
-runtime: don't call cgocallback from signal handler (CL 30218)
-runtime: fix check for vacuous page boundary rounding (CL 27230)
-runtime: fix map iterator concurrent map check (CL 24749)
-runtime: fix newextram PC passed to race detector (CL 29712)
-runtime: implement unconditional hybrid barrier (CL 31765)
-runtime: include pre-panic/throw logs in core dumps (CL 32013)
-runtime: limit the number of map overflow buckets (CL 25049)
-runtime: pass windows float syscall args via XMM (CL 32173)
-runtime: print sigcode on signal crash (CL 32183)
-runtime: record current PC for SIGPROF on non-Go thread (CL 30252)
-runtime: sleep on CLOCK_MONOTONIC in futexsleep1 on freebsd (CL 30154)
diff --git a/doc/go1.9.html b/doc/go1.9.html
new file mode 100644
index 0000000..be0ceef
--- /dev/null
+++ b/doc/go1.9.html
@@ -0,0 +1,985 @@
+<!--{
+ "Title": "Go 1.9 Release Notes",
+ "Path": "/doc/go1.9",
+ "Template": true
+}-->
+
+<!--
+NOTE: In this document and others in this directory, the convention is to
+set fixed-width phrases with non-fixed-width spaces, as in
+<code>hello</code> <code>world</code>.
+Do not send CLs removing the interior tags from such phrases.
+-->
+
+<style>
+ul li { margin: 0.5em 0; }
+</style>
+
+<h2 id="introduction">DRAFT RELEASE NOTES - Introduction to Go 1.9</h2>
+
+<p><strong>
+ Go 1.9 is not yet released. These are work-in-progress
+ release notes. Go 1.9 is expected to be released in August 2017.
+</strong></p>
+
+<p>
+ The latest Go release, version 1.9, arrives six months
+ after <a href="go1.8">Go 1.8</a> and is the tenth release in
+ the <a href="https://golang.org/doc/devel/release.html">Go 1.x
+ series</a>.
+ There are two <a href="#language">changes to the language</a>:
+ adding support for type aliases and defining when implementations
+ may fuse floating point operations.
+ Most of the changes are in the implementation of the toolchain,
+ runtime, and libraries.
+ As always, the release maintains the Go 1
+ <a href="/doc/go1compat.html">promise of compatibility</a>.
+ We expect almost all Go programs to continue to compile and run as
+ before.
+</p>
+
+<p>
+ The release
+ adds <a href="#monotonic-time">transparent monotonic time support</a>,
+ <a href="#parallel-compile">parallelizes compilation of functions</a> within a package,
+ better supports <a href="#test-helper">test helper functions</a>,
+ includes a new <a href="#math-bits">bit manipulation package</a>,
+ and has a new <a href="#sync-map">concurrent map type</a>.
+</p>
+
+<h2 id="language">Changes to the language</h2>
+
+<p>
+ There are two changes to the language.
+</p>
+<p>
+ Go now supports type aliases to support gradual code repair while
+ moving a type between packages.
+ The <a href="https://golang.org/design/18130-type-alias">type alias
+ design document</a>
+ and <a href="https://talks.golang.org/2016/refactor.article">an
+ article on refactoring</a> cover the problem in detail.
+ In short, a type alias declaration has the form:
+</p>
+
+<pre>
+type T1 = T2
+</pre>
+
+<p>
+ This declaration introduces an alias name <code>T1</code>—an
+ alternate spelling—for the type denoted by <code>T2</code>; that is,
+ both <code>T1</code> and <code>T2</code> denote the same type.
+</p>
+
+<p> <!-- CL 40391 -->
+ A smaller language change is that the
+ <a href="/ref/spec#Floating_point_operators">language specification
+ now states</a> when implementations are allowed to fuse floating
+ point operations together, such as by using an architecture's "fused
+ multiply and add" (FMA) instruction to compute <code>x*y</code> <code>+</code> <code>z</code>
+ without rounding the intermediate result <code>x*y</code>.
+ To force the intermediate rounding, write <code>float64(x*y)</code> <code>+</code> <code>z</code>.
+</p>
+
+<h2 id="ports">Ports</h2>
+
+<p>
+ There are no new supported operating systems or processor
+ architectures in this release.
+</p>
+
+<h3 id="power8">ppc64x requires POWER8</h3>
+
+<p> <!-- CL 36725, CL 36832 -->
+ Both <code>GOARCH=ppc64</code> and <code>GOARCH=ppc64le</code> now
+ require at least POWER8 support. In previous releases,
+ only <code>GOARCH=ppc64le</code> required POWER8 and the big
+ endian <code>ppc64</code> architecture supported older
+ hardware.
+<p>
+
+<h3 id="freebsd">FreeBSD</h3>
+
+<p>
+ Go 1.9 is the last release that will run on FreeBSD 9.3,
+ which is already
+ <a href="https://www.freebsd.org/security/unsupported.html">unsupported by FreeBSD</a>.
+ Go 1.10 will require FreeBSD 10.3+.
+</p>
+
+<h3 id="openbsd">OpenBSD 6.0</h3>
+
+<p> <!-- CL 40331 -->
+ Go 1.9 now enables PT_TLS generation for cgo binaries and thus
+ requires OpenBSD 6.0 or newer. Go 1.9 no longer supports
+ OpenBSD 5.9.
+<p>
+
+<h3 id="known_issues">Known Issues</h3>
+
+<p>
+ There are some instabilities on FreeBSD that are known but not understood.
+ These can lead to program crashes in rare cases.
+ See <a href="https://golang.org/issue/15658">issue 15658</a>.
+ Any help in solving this FreeBSD-specific issue would be appreciated.
+</p>
+
+<p>
+ Go stopped running NetBSD builders during the Go 1.9 development
+ cycle due to NetBSD kernel crashes, up to and including NetBSD 7.1.
+ As Go 1.9 is being released, NetBSD 7.1.1 is being released with a fix.
+ However, at this time we have no NetBSD builders passing our test suite.
+ Any help investigating the
+ <a href="https://github.com/golang/go/labels/OS-NetBSD">various NetBSD issues</a>
+ would be appreciated.
+</p>
+
+<h2 id="tools">Tools</h2>
+
+<h3 id="parallel-compile">Parallel Compilation</h3>
+
+<p>
+ The Go compiler now supports compiling a package's functions in parallel, taking
+ advantage of multiple cores. This is in addition to the <code>go</code> command's
+ existing support for parallel compilation of separate packages.
+ Parallel compilation is on by default, but it can be disabled by setting the
+ environment variable <code>GO19CONCURRENTCOMPILATION</code> to <code>0</code>.
+</p>
+
+<h3 id="vendor-dotdotdot">Vendor matching with ./...</h3>
+
+<p><!-- CL 38745 -->
+ By popular request, <code>./...</code> no longer matches packages
+ in <code>vendor</code> directories in tools accepting package names,
+ such as <code>go</code> <code>test</code>. To match vendor
+ directories, write <code>./vendor/...</code>.
+</p>
+
+<h3 id="compiler">Compiler Toolchain</h3>
+
+<p><!-- CL 37441 -->
+ Complex division is now C99-compatible. This has always been the
+ case in gccgo and is now fixed in the gc toolchain.
+</p>
+
+<p> <!-- CL 36983 -->
+ The linker will now generate DWARF information for cgo executables on Windows.
+</p>
+
+<p> <!-- CL 44210, CL 40095 -->
+ The compiler now includes lexical scopes in the generated DWARF if the
+ <code>-N -l</code> flags are provided, allowing
+ debuggers to hide variables that are not in scope. The <code>.debug_info</code>
+ section is now DWARF version 4.
+</p>
+
+<p> <!-- CL 43855 -->
+ The values of <code>GOARM</code> and <code>GO386</code> now affect a
+ compiled package's build ID, as used by the <code>go</code> tool's
+ dependency caching.
+</p>
+
+<h3 id="asm">Assembler</h3>
+
+<p> <!-- CL 42028 -->
+ The four-operand ARM <code>MULA</code> instruction is now assembled correctly,
+ with the addend register as the third argument and the result
+ register as the fourth and final argument.
+ In previous releases, the two meanings were reversed.
+ The three-operand form, in which the fourth argument is implicitly
+ the same as the third, is unaffected.
+ Code using four-operand <code>MULA</code> instructions
+ will need to be updated, but we believe this form is very rarely used.
+ <code>MULAWT</code> and <code>MULAWB</code> were already
+ using the correct order in all forms and are unchanged.
+</p>
+
+<p> <!-- CL 42990 -->
+ The assembler now supports <code>ADDSUBPS/PD</code>, completing the
+ two missing x86 SSE3 instructions.
+</p>
+
+<h3 id="go-doc">Doc</h3>
+
+<p><!-- CL 36031 -->
+ Long lists of arguments are now truncated. This improves the readability
+ of <code>go</code> <code>doc</code> on some generated code.
+</p>
+
+<p><!-- CL 38438 -->
+ Viewing documentation on struct fields is now supported.
+ For example, <code>go</code> <code>doc</code> <code>http.Client.Jar</code>.
+</p>
+
+<h3 id="go-env-json">Env</h3>
+
+<p> <!-- CL 38757 -->
+ The new <code>go</code> <code>env</code> <code>-json</code> flag
+ enables JSON output, instead of the default OS-specific output
+ format.
+</p>
+
+<h3 id="go-test-list">Test</h3>
+
+<p> <!-- CL 41195 -->
+ The <a href="/cmd/go/#hdr-Description_of_testing_flags"><code>go</code> <code>test</code></a>
+ command accepts a new <code>-list</code> flag, which takes a regular
+ expression as an argument and prints to stdout the name of any
+ tests, benchmarks, or examples that match it, without running them.
+</p>
+
+
+<h3 id="go-tool-pprof">Pprof</h3>
+
+<p> <!-- CL 34192 -->
+ Profiles produced by the <code>runtime/pprof</code> package now
+ include symbol information, so they can be viewed
+ in <code>go</code> <code>tool</code> <code>pprof</code>
+ without the binary that produced the profile.
+</p>
+
+<p> <!-- CL 38343 -->
+ The <code>go</code> <code>tool</code> <code>pprof</code> command now
+ uses the HTTP proxy information defined in the environment, using
+ <a href="/pkg/net/http/#ProxyFromEnvironment"><code>http.ProxyFromEnvironment</code></a>.
+</p>
+
+<h3 id="vet">Vet</h3>
+
+<!-- CL 40112 -->
+<p>
+ The <a href="/cmd/vet/"><code>vet</code> command</a>
+ has been better integrated into the
+ <a href="/cmd/go/"><code>go</code> tool</a>,
+ so <code>go</code> <code>vet</code> now supports all standard build
+ flags while <code>vet</code>'s own flags are now available
+ from <code>go</code> <code>vet</code> as well as
+ from <code>go</code> <code>tool</code> <code>vet</code>.
+</p>
+
+<h3 id="gccgo">Gccgo</h3>
+
+<p>
+Due to the alignment of Go's semiannual release schedule with GCC's
+annual release schedule,
+GCC release 7 contains the Go 1.8.3 version of gccgo.
+We expect that the next release, GCC 8, will contain the Go 1.10
+version of gccgo.
+</p>
+
+<h2 id="runtime">Runtime</h2>
+
+<h3 id="callersframes">Call stacks with inlined frames</h3>
+
+<p>
+ Users of
+ <a href="/pkg/runtime#Callers"><code>runtime.Callers</code></a>
+ should avoid directly inspecting the resulting PC slice and instead use
+ <a href="/pkg/runtime#CallersFrames"><code>runtime.CallersFrames</code></a>
+ to get a complete view of the call stack, or
+ <a href="/pkg/runtime#Caller"><code>runtime.Caller</code></a>
+ to get information about a single caller.
+ This is because an individual element of the PC slice cannot account
+ for inlined frames or other nuances of the call stack.
+</p>
+
+<p>
+ Specifically, code that directly iterates over the PC slice and uses
+ functions such as
+ <a href="/pkg/runtime#FuncForPC"><code>runtime.FuncForPC</code></a>
+ to resolve each PC individually will miss inlined frames.
+ To get a complete view of the stack, such code should instead use
+ <code>CallersFrames</code>.
+ Likewise, code should not assume that the length returned by
+ <code>Callers</code> is any indication of the call depth.
+ It should instead count the number of frames returned by
+ <code>CallersFrames</code>.
+</p>
+
+<p>
+ Code that queries a single caller at a specific depth should use
+ <code>Caller</code> rather than passing a slice of length 1 to
+ <code>Callers</code>.
+</p>
+
+<p>
+ <a href="/pkg/runtime#CallersFrames"><code>runtime.CallersFrames</code></a>
+ has been available since Go 1.7, so code can be updated prior to
+ upgrading to Go 1.9.
+</p>
+
+<h2 id="performance">Performance</h2>
+
+<p>
+ As always, the changes are so general and varied that precise
+ statements about performance are difficult to make. Most programs
+ should run a bit faster, due to speedups in the garbage collector,
+ better generated code, and optimizations in the core library.
+</p>
+
+<h3 id="gc">Garbage Collector</h3>
+
+<p> <!-- CL 37520 -->
+ Library functions that used to trigger stop-the-world garbage
+ collection now trigger concurrent garbage collection.
+
+ Specifically, <a href="/pkg/runtime/#GC"><code>runtime.GC</code></a>,
+ <a href="/pkg/runtime/debug/#SetGCPercent"><code>debug.SetGCPercent</code></a>,
+ and
+ <a href="/pkg/runtime/debug/#FreeOSMemory"><code>debug.FreeOSMemory</code></a>,
+ now trigger concurrent garbage collection, blocking only the calling
+ goroutine until the garbage collection is done.
+</p>
+
+<p> <!-- CL 34103, CL 39835 -->
+ The
+ <a href="/pkg/runtime/debug/#SetGCPercent"><code>debug.SetGCPercent</code></a>
+ function only triggers a garbage collection if one is immediately
+ necessary because of the new GOGC value.
+ This makes it possible to adjust GOGC on-the-fly.
+</p>
+
+<p> <!-- CL 38732 -->
+ Large object allocation performance is significantly improved in
+ applications using large (>50GB) heaps containing many large
+ objects.
+</p>
+
+<p> <!-- CL 34937 -->
+ The <a href="/pkg/runtime/#ReadMemStats"><code>runtime.ReadMemStats</code></a>
+ function now takes less than 100µs even for very large heaps.
+</p>
+
+<h2 id="library">Core library</h2>
+
+<h3 id="monotonic-time">Transparent Monotonic Time support</h3>
+
+<p> <!-- CL 36255 -->
+ The <a href="/pkg/time/"><code>time</code></a> package now transparently
+ tracks monotonic time in each <a href="/pkg/time/#Time"><code>Time</code></a>
+ value, making computing durations between two <code>Time</code> values
+ a safe operation in the presence of wall clock adjustments.
+ See the <a href="/pkg/time/#hdr-Monotonic_Clocks">package docs</a> and
+ <a href="https://golang.org/design/12914-monotonic">design document</a>
+ for details.
+</p>
+
+<h3 id="math-bits">New bit manipulation package</h3>
+
+<p> <!-- CL 36315 -->
+ Go 1.9 includes a new package,
+ <a href="/pkg/math/bits/"><code>math/bits</code></a>, with optimized
+ implementations for manipulating bits. On most architectures,
+ functions in this package are additionally recognized by the
+ compiler and treated as intrinsics for additional performance.
+</p>
+
+<h3 id="test-helper">Test Helper Functions</h3>
+
+<p> <!-- CL 38796 -->
+ The
+ new <a href="/pkg/testing/#T.Helper"><code>(*T).Helper</code></a>
+ and <a href="/pkg/testing/#B.Helper"><code>(*B).Helper</code></a>
+ methods mark the calling function as a test helper function. When
+ printing file and line information, that function will be skipped.
+ This permits writing test helper functions while still having useful
+ line numbers for users.
+</p>
+
+<h3 id="sync-map">Concurrent Map</h3>
+
+<p> <!-- CL 36617 -->
+ The new <a href="/pkg/sync/#Map"><code>Map</code></a> type
+ in the <a href="/pkg/sync/"><code>sync</code></a> package
+ is a concurrent map with amortized-constant-time loads, stores, and
+ deletes. It is safe for multiple goroutines to call a <code>Map</code>'s methods
+ concurrently.
+</p>
+
+<h3 id="pprof-labels">Profiler Labels</h3>
+
+<p><!-- CL 34198 -->
+ The <a href="/pkg/runtime/pprof"><code>runtime/pprof</code> package</a>
+ now supports adding labels to <code>pprof</code> profiler records.
+ Labels form a key-value map that is used to distinguish calls of the
+ same function in different contexts when looking at profiles
+ with the <a href="/cmd/pprof/"><code>pprof</code> command</a>.
+ The <code>pprof</code> package's
+ new <a href="/pkg/runtime/pprof/#Do"><code>Do</code> function</a>
+ runs code associated with some provided labels. Other new functions
+ in the package help work with labels.
+</p>
+
+</dl><!-- runtime/pprof -->
+
+
+<h3 id="minor_library_changes">Minor changes to the library</h3>
+
+<p>
+ As always, there are various minor changes and updates to the library,
+ made with the Go 1 <a href="/doc/go1compat">promise of compatibility</a>
+ in mind.
+</p>
+
+<dl id="archive/zip"><dt><a href="/pkg/archive/zip/">archive/zip</a></dt>
+ <dd>
+ <p><!-- CL 39570 -->
+ The
+ ZIP <a href="/pkg/archive/zip/#Writer"><code>Writer</code></a>
+ now sets the UTF-8 bit in
+ the <a href="/pkg/archive/zip/#FileHeader.Flags"><code>FileHeader.Flags</code></a>
+ when appropriate.
+ </p>
+
+</dl><!-- archive/zip -->
+
+<dl id="crypto/rand"><dt><a href="/pkg/crypto/rand/">crypto/rand</a></dt>
+ <dd>
+ <p><!-- CL 43852 -->
+ On Linux, Go now calls the <code>getrandom</code> system call
+ without the <code>GRND_NONBLOCK</code> flag; it will now block
+ until the kernel has sufficient randomness. On kernels predating
+ the <code>getrandom</code> system call, Go continues to read
+ from <code>/dev/urandom</code>.
+ </p>
+
+</dl><!-- crypto/rand -->
+
+<dl id="crypto/x509"><dt><a href="/pkg/crypto/x509/">crypto/x509</a></dt>
+ <dd>
+ <p><!-- CL 36093 -->
+
+ On Unix systems the environment
+ variables <code>SSL_CERT_FILE</code>
+ and <code>SSL_CERT_DIR</code> can now be used to override the
+ system default locations for the SSL certificate file and SSL
+ certificate files directory, respectively.
+ </p>
+
+ <p>The FreeBSD file <code>/usr/local/etc/ssl/cert.pem</code> is
+ now included in the certificate search path.
+ </p>
+
+ <p><!-- CL 36900 -->
+
+ The package now supports excluded domains in name constraints.
+ In addition to enforcing such constraints,
+ <a href="/pkg/crypto/x509/#CreateCertificate"><code>CreateCertificate</code></a>
+ will create certificates with excluded name constraints
+ if the provided template certificate has the new
+ field
+ <a href="/pkg/crypto/x509/#Certificate.ExcludedDNSDomains"><code>ExcludedDNSDomains</code></a>
+ populated.
+ </p>
+
+</dl><!-- crypto/x509 -->
+
+<dl id="database/sql"><dt><a href="/pkg/database/sql/">database/sql</a></dt>
+ <dd>
+ <p><!-- CL 35476 -->
+ The package will now use a cached <a href="/pkg/database/sql/#Stmt"><code>Stmt</code></a> if
+ available in <a href="/pkg/database/sql/#Tx.Stmt"><code>Tx.Stmt</code></a>.
+ This prevents statements from being re-prepared each time
+ <a href="/pkg/database/sql/#Tx.Stmt"><code>Tx.Stmt</code></a> is called.
+ </p>
+
+ <p><!-- CL 38533 -->
+ The package now allows drivers to implement their own argument checkers by implementing
+ <a href="/pkg/database/sql/driver/#NamedValueChecker"><code>driver.NamedValueChecker</code></a>.
+ This also allows drivers to support <code>OUTPUT</code> and <code>INOUT</code> parameter types.
+ <a href="/pkg/database/sql/#Out"><code>Out</code></a> should be used to return output parameters
+ when supported by the driver.
+ </p>
+
+ <p><!-- CL 39031 -->
+ <a href="/pkg/database/sql/#Rows.Scan"><code>Rows.Scan</code></a> can now scan user-defined string types.
+ Previously the package supported scanning into numeric types like <code>type</code> <code>Int</code> <code>int64</code>. It now also supports
+ scanning into string types like <code>type</code> <code>String</code> <code>string</code>.
+ </p>
+
+ <p><!-- CL 40694 -->
+ The new <a href="/pkg/database/sql/#DB.Conn"><code>DB.Conn</code></a> method returns the new
+ <a href="/pkg/database/sql/#Conn"><code>Conn</code></a> type representing an
+ exclusive connection to the database from the connection pool. All queries run on
+ a <a href="/pkg/database/sql/#Conn"><code>Conn</code></a> will use the same underlying
+ connection until <a href="/pkg/database/sql/#Conn.Close"><code>Conn.Close</code></a> is called
+ to return the connection to the connection pool.
+ </p>
+
+</dl><!-- database/sql -->
+
+<dl id="encoding/asn1"><dt><a href="/pkg/encoding/asn1/">encoding/asn1</a></dt>
+ <dd>
+ <p><!-- CL 38660 -->
+ The new
+ <a href="/pkg/encoding/asn1/#NullBytes"><code>NullBytes</code></a>
+ and
+ <a href="/pkg/encoding/asn1/#NullRawValue"><code>NullRawValue</code></a>
+ represent the ASN.1 NULL type.
+ </p>
+
+</dl><!-- encoding/asn1 -->
+
+<dl id="encoding/base32"><dt><a href="/pkg/encoding/base32/">encoding/base32</a></dt>
+ <dd>
+ <p><!-- CL 38634 -->
+ The new <a href="/pkg/encoding/base32/#Encoding.WithPadding">Encoding.WithPadding</a>
+ method adds support for custom padding characters and disabling padding.
+ </p>
+
+</dl><!-- encoding/base32 -->
+
+<dl id="encoding/csv"><dt><a href="/pkg/encoding/csv/">encoding/csv</a></dt>
+ <dd>
+ <p><!-- CL 41730 -->
+ The new field
+ <a href="/pkg/encoding/csv/#Reader.ReuseRecord"><code>Reader.ReuseRecord</code></a>
+ controls whether calls to
+ <a href="/pkg/encoding/csv/#Reader.Read"><code>Read</code></a>
+ may return a slice sharing the backing array of the previous
+ call's returned slice for improved performance.
+ </p>
+
+</dl><!-- encoding/csv -->
+
+<dl id="fmt"><dt><a href="/pkg/fmt/">fmt</a></dt>
+ <dd>
+ <p><!-- CL 37051 -->
+ The sharp flag ('<code>#</code>') is now supported when printing
+ floating point and complex numbers. It will always print a
+ decimal point
+ for <code>%e</code>, <code>%E</code>, <code>%f</code>, <code>%F</code>, <code>%g</code>
+ and <code>%G</code>; it will not remove trailing zeros
+ for <code>%g</code> and <code>%G</code>.
+ </p>
+
+</dl><!-- fmt -->
+
+<dl id="hash/fnv"><dt><a href="/pkg/hash/fnv/">hash/fnv</a></dt>
+ <dd>
+ <p><!-- CL 38356 -->
+ The package now includes 128-bit FNV-1 and FNV-1a hash support with
+ <a href="/pkg/hash/fnv/#New128"><code>New128</code></a> and
+ <a href="/pkg/hash/fnv/#New128a"><code>New128a</code></a>, respectively.
+ </p>
+
+</dl><!-- hash/fnv -->
+
+<dl id="html/template"><dt><a href="/pkg/html/template/">html/template</a></dt>
+ <dd>
+ <p><!-- CL 37880, CL 40936 -->
+ The package now reports an error if a predefined escaper (one of
+ "html", "urlquery" and "js") is found in a pipeline and does not match
+ what the auto-escaper would have decided on its own.
+ This avoids certain security or correctness issues.
+ Now use of one of these escapers is always either a no-op or an error.
+ (The no-op case eases migration from <a href="/pkg/text/template/">text/template</a>.)
+ </p>
+
+</dl><!-- html/template -->
+
+<dl id="image"><dt><a href="/pkg/image/">image</a></dt>
+ <dd>
+ <p><!-- CL 36734 -->
+ The <a href="/pkg/image/#Rectangle.Intersect"><code>Rectangle.Intersect</code></a>
+ method now returns a zero <code>Rectangle</code> when called on
+ adjacent but non-overlapping rectangles, as documented. In
+ earlier releases it would incorrectly return an empty but
+ non-zero <code>Rectangle</code>.
+ </p>
+
+</dl><!-- image -->
+
+<dl id="image/color"><dt><a href="/pkg/image/color/">image/color</a></dt>
+ <dd>
+ <p><!-- CL 36732 -->
+ The YCbCr to RGBA conversion formula has been tweaked to ensure
+ that rounding adjustments span the complete [0, 0xffff] RGBA
+ range.
+ </p>
+
+</dl><!-- image/color -->
+
+<dl id="image/png"><dt><a href="/pkg/image/png/">image/png</a></dt>
+ <dd>
+ <p><!-- CL 34150 -->
+ The new <a href="/pkg/image/png/#Encoder.BufferPool"><code>Encoder.BufferPool</code></a>
+ field allows specifying an <a href="/pkg/image/png/#EncoderBufferPool"><code>EncoderBufferPool</code></a>,
+ that will be used by the encoder to get temporary <code>EncoderBuffer</code>
+ buffers when encoding a PNG image.
+
+ The use of a <code>BufferPool</code> reduces the number of
+ memory allocations performed while encoding multiple images.
+ </p>
+
+ <p><!-- CL 38271 -->
+ The package now supports the decoding of transparent 8-bit
+ grayscale ("Gray8") images.
+ </p>
+
+</dl><!-- image/png -->
+
+<dl id="math/big"><dt><a href="/pkg/math/big/">math/big</a></dt>
+ <dd>
+ <p><!-- CL 36487 -->
+ The new
+ <a href="/pkg/math/big/#Int.IsInt64"><code>IsInt64</code></a>
+ and
+ <a href="/pkg/math/big/#Int.IsUint64"><code>IsUint64</code></a>
+ methods report whether an <code>Int</code>
+ may be represented as an <code>int64</code> or <code>uint64</code>
+ value.
+ </p>
+
+</dl><!-- math/big -->
+
+<dl id="mime/multipart"><dt><a href="/pkg/mime/multipart/">mime/multipart</a></dt>
+ <dd>
+ <p><!-- CL 39223 -->
+ The new
+ <a href="/pkg/mime/multipart/#FileHeader.Size"><code>FileHeader.Size</code></a>
+ field describes the size of a file in a multipart message.
+ </p>
+
+</dl><!-- mime/multipart -->
+
+<dl id="net"><dt><a href="/pkg/net/">net</a></dt>
+ <dd>
+ <p><!-- CL 32572 -->
+ The new
+ <a href="/pkg/net/#Resolver.StrictErrors"><code>Resolver.StrictErrors</code></a>
+ provides control over how Go's built-in DNS resolver handles
+ temporary errors during queries composed of multiple sub-queries,
+ such as an A+AAAA address lookup.
+ </p>
+
+ <p><!-- CL 37260 -->
+ The new
+ <a href="/pkg/net/#Resolver.Dial"><code>Resolver.Dial</code></a>
+ allows a <code>Resolver</code> to use a custom dial function.
+ </p>
+
+ <p><!-- CL 40510 -->
+ <a href="/pkg/net/#JoinHostPort"><code>JoinHostPort</code></a> now only places an address in square brackets if the host contains a colon.
+ In previous releases it would also wrap addresses in square brackets if they contained a percent ('<code>%</code>') sign.
+ </p>
+
+ <p><!-- CL 37913 -->
+ The new methods
+ <a href="/pkg/net/#TCPConn.SyscallConn"><code>TCPConn.SyscallConn</code></a>,
+ <a href="/pkg/net/#IPConn.SyscallConn"><code>IPConn.SyscallConn</code></a>,
+ <a href="/pkg/net/#UDPConn.SyscallConn"><code>UDPConn.SyscallConn</code></a>,
+ and
+ <a href="/pkg/net/#UnixConn.SyscallConn"><code>UnixConn.SyscallConn</code></a>
+ provide access to the connections' underlying file descriptors.
+ </p>
+
+ <p><!-- 45088 -->
+ It is now safe to call <a href="/pkg/net/#Dial"><code>Dial</code></a> with the address obtained from
+ <code>(*TCPListener).String()</code> after creating the listener with
+ <code><a href="/pkg/net/#Listen">Listen</a>("tcp", ":0")</code>.
+ Previously it failed on some machines with half-configured IPv6 stacks.
+ </p>
+
+</dl><!-- net -->
+
+<dl id="net/http"><dt><a href="/pkg/net/http/">net/http</a></dt>
+ <dd>
+
+ <p><!-- CL 37328 -->
+ The <a href="/pkg/net/http/#Cookie.String"><code>Cookie.String</code></a> method, used for
+ <code>Cookie</code> and <code>Set-Cookie</code> headers, now encloses values in double quotes
+ if the value contains either a space or a comma.
+ </p>
+
+ <p>Server changes:</p>
+ <ul>
+ <li><!-- CL 38194 -->
+ <a href="/pkg/net/http/#ServeMux"><code>ServeMux</code></a> now ignores ports in the host
+ header when matching handlers. The host is matched unmodified for <code>CONNECT</code> requests.
+ </li>
+
+ <li><!-- CL 34727 -->
+ <a href="/pkg/net/http/#Server.WriteTimeout"><code>Server.WriteTimeout</code></a>
+ now applies to HTTP/2 connections and is enforced per-stream.
+ </li>
+
+ <li><!-- CL 43231 -->
+ HTTP/2 now uses the priority write scheduler by default.
+ Frames are scheduled by following HTTP/2 priorities as described in
+ <a href="https://tools.ietf.org/html/rfc7540#section-5.3">RFC 7540 Section 5.3</a>.
+ </li>
+
+ <li><!-- CL 36483 -->
+ The HTTP handler returned by <a href="/pkg/net/http/#StripPrefix"><code>StripPrefix</code></a>
+ now calls its provided handler with a modified clone of the original <code>*http.Request</code>.
+ Any code storing per-request state in maps keyed by <code>*http.Request</code> should
+ use
+ <a href="/pkg/net/http/#Request.Context"><code>Request.Context</code></a>,
+ <a href="/pkg/net/http/#Request.WithContext"><code>Request.WithContext</code></a>,
+ and
+ <a href="/pkg/context/#WithValue"><code>context.WithValue</code></a> instead.
+ </li>
+ </ul>
+
+ <p>Client & Transport changes:</p>
+ <ul>
+ <li><!-- CL 35488 -->
+ The <a href="/pkg/net/http/#Transport"><code>Transport</code></a>
+ now supports making requests via SOCKS5 proxy when the URL returned by
+ <a href="/net/http/#Transport.Proxy"><code>Transport.Proxy</code></a>
+ has the scheme <code>socks5</code>.
+ </li>
+ </ul>
+
+</dl><!-- net/http -->
+
+<dl id="net/http/fcgi"><dt><a href="/pkg/net/http/fcgi/">net/http/fcgi</a></dt>
+ <dd>
+ <p><!-- CL 40012 -->
+ The new
+ <a href="/pkg/net/http/fcgi/#ProcessEnv"><code>ProcessEnv</code></a>
+ function returns FastCGI environment variables associated with an HTTP request
+ for which there are no appropriate
+ <a href="/pkg/net/http/#Request"><code>http.Request</code></a>
+ fields, such as <code>REMOTE_USER</code>.
+ </p>
+
+</dl><!-- net/http/fcgi -->
+
+<dl id="net/http/httptest"><dt><a href="/pkg/net/http/httptest/">net/http/httptest</a></dt>
+ <dd>
+ <p><!-- CL 34639 -->
+ The new
+ <a href="/pkg/net/http/httptest/#Server.Client"><code>Server.Client</code></a>
+ method returns an HTTP client configured for making requests to the test server.
+ </p>
+
+ <p>
+ The new
+ <a href="/pkg/net/http/httptest/#Server.Certificate"><code>Server.Certificate</code></a>
+ method returns the test server's TLS certificate, if any.
+ </p>
+
+</dl><!-- net/http/httptest -->
+
+<dl id="os"><dt><a href="/pkg/os/">os</a></dt>
+ <dd>
+ <p><!-- CL 36800 -->
+ The <code>os</code> package now uses the internal runtime poller
+ for file I/O.
+ This reduces the number of threads required for read/write
+ operations on pipes, and it eliminates races when one goroutine
+ closes a file while another is using the file for I/O.
+ </p>
+
+ <dd>
+ <p><!-- CL 37915 -->
+ On Windows,
+ <a href="/pkg/os/#Args"><code>Args</code></a>
+ is now populated without <code>shell32.dll</code>, improving process start-up time by 1-7 ms.
+ </p>
+
+</dl><!-- os -->
+
+<dl id="os/exec"><dt><a href="/pkg/os/exec/">os/exec</a></dt>
+ <dd>
+ <p><!-- CL 37586 -->
+ The <code>os/exec</code> package now prevents child processes from being created with
+ any duplicate environment variables.
+ If <a href="/pkg/os/exec/#Cmd.Env"><code>Cmd.Env</code></a>
+ contains duplicate environment keys, only the last
+ value in the slice for each duplicate key is used.
+ </p>
+
+</dl><!-- os/exec -->
+
+<dl id="os/user"><dt><a href="/pkg/os/user/">os/user</a></dt>
+ <dd>
+ <p><!-- CL 37664 -->
+ <a href="/pkg/os/user/#Lookup"><code>Lookup</code></a> and
+ <a href="/pkg/os/user/#LookupId"><code>LookupId</code></a> now
+ work on Unix systems when <code>CGO_ENABLED=0</code> by reading
+ the <code>/etc/passwd</code> file.
+ </p>
+
+ <p><!-- CL 33713 -->
+ <a href="/pkg/os/user/#LookupGroup"><code>LookupGroup</code></a> and
+ <a href="/pkg/os/user/#LookupGroupId"><code>LookupGroupId</code></a> now
+ work on Unix systems when <code>CGO_ENABLED=0</code> by reading
+ the <code>/etc/group</code> file.
+ </p>
+
+</dl><!-- os/user -->
+
+<dl id="reflect"><dt><a href="/pkg/reflect/">reflect</a></dt>
+ <dd>
+ <p><!-- CL 38335 -->
+ The new
+ <a href="/pkg/reflect/#MakeMapWithSize"><code>MakeMapWithSize</code></a>
+ function creates a map with a capacity hint.
+ </p>
+
+</dl><!-- reflect -->
+
+<dl id="runtime"><dt><a href="/pkg/runtime/">runtime</a></dt>
+ <dd>
+ <p><!-- CL 37233, CL 37726 -->
+ Tracebacks generated by the runtime and recorded in profiles are
+ now accurate in the presence of inlining.
+ To retrieve tracebacks programmatically, applications should use
+ <a href="/pkg/runtime/#CallersFrames"><code>runtime.CallersFrames</code></a>
+ rather than directly iterating over the results of
+ <a href="/pkg/runtime/#Callers"><code>runtime.Callers</code></a>.
+ </p>
+
+ <p><!-- CL 38403 -->
+ On Windows, Go no longer forces the system timer to run at high
+ resolution when the program is idle.
+ This should reduce the impact of Go programs on battery life.
+ </p>
+
+ <p><!-- CL 29341 -->
+ On FreeBSD, <code>GOMAXPROCS</code> and
+ <a href="/pkg/runtime/#NumCPU"><code>runtime.NumCPU</code></a>
+ are now based on the process' CPU mask, rather than the total
+ number of CPUs.
+ </p>
+
+ <p><!-- CL 43641 -->
+ The runtime has preliminary support for Android O.
+ </p>
+
+</dl><!-- runtime -->
+
+<dl id="runtime/debug"><dt><a href="/pkg/runtime/debug/">runtime/debug</a></dt>
+ <dd>
+ <p><!-- CL 34013 -->
+ Calling
+ <a href="/pkg/runtime/debug/#SetGCPercent"><code>SetGCPercent</code></a>
+ with a negative value no longer runs an immediate garbage collection.
+ </p>
+
+</dl><!-- runtime/debug -->
+
+<dl id="runtime/trace"><dt><a href="/pkg/runtime/trace/">runtime/trace</a></dt>
+ <dd>
+ <p><!-- CL 36015 -->
+ The execution trace now displays mark assist events, which
+ indicate when an application goroutine is forced to assist
+ garbage collection because it is allocating too quickly.
+ </p>
+
+ <p><!-- CL 40810 -->
+ "Sweep" events now encompass the entire process of finding free
+ space for an allocation, rather than recording each individual
+ span that is swept.
+ This reduces allocation latency when tracing allocation-heavy
+ programs.
+ The sweep event shows how many bytes were swept and how many
+ were reclaimed.
+ </p>
+
+</dl><!-- runtime/trace -->
+
+<dl id="sync"><dt><a href="/pkg/sync/">sync</a></dt>
+ <dd>
+ <p><!-- CL 34310 -->
+ <a href="/pkg/sync/#Mutex"><code>Mutex</code></a> is now more fair.
+ </p>
+
+</dl><!-- sync -->
+
+<dl id="syscall"><dt><a href="/pkg/syscall/">syscall</a></dt>
+ <dd>
+ <p><!-- CL 36697 -->
+ The new field
+ <a href="/pkg/syscall/#Credential.NoSetGroups"><code>Credential.NoSetGroups</code></a>
+ controls whether Unix systems make a <code>setgroups</code> system call
+ to set supplementary groups when starting a new process.
+ </p>
+
+ <p><!-- CL 43512 -->
+ The new field
+ <a href="/pkg/syscall/#SysProcAttr.AmbientCaps"><code>SysProcAttr.AmbientCaps</code></a>
+ allows setting ambient capabilities on Linux 4.3+ when creating
+ a new process.
+ </p>
+
+ <p><!-- CL 37439 -->
+ On 64-bit x86 Linux, process creation latency has been optimized with
+ use of <code>CLONE_VFORK</code> and <code>CLONE_VM</code>.
+ </p>
+
+ <p><!-- CL 37913 -->
+ The new
+ <a href="/pkg/syscall/#Conn"><code>Conn</code></a>
+ interface describes some types in the
+ <a href="/pkg/net/"><code>net</code></a>
+ package that can provide access to their underlying file descriptor
+ using the new
+ <a href="/pkg/syscall/#RawConn"><code>RawConn</code></a>
+ interface.
+ </p>
+
+</dl><!-- syscall -->
+
+
+<dl id="testing/quick"><dt><a href="/pkg/testing/quick/">testing/quick</a></dt>
+ <dd>
+ <p><!-- CL 39152 -->
+ The package now chooses values in the full range when
+ generating <code>int64</code> and <code>uint64</code> random
+ numbers; in earlier releases generated values were always
+ limited to the [-2<sup>62</sup>, 2<sup>62</sup>) range.
+ </p>
+
+ <p>
+ In previous releases, using a nil
+ <a href="/pkg/testing/quick/#Config.Rand"><code>Config.Rand</code></a>
+ value caused a fixed deterministic random number generator to be used.
+ It now uses a random number generator seeded with the current time.
+ For the old behavior, set <code>Config.Rand</code> to <code>rand.New(rand.NewSource(0))</code>.
+ </p>
+
+</dl><!-- testing/quick -->
+
+<dl id="text/template"><dt><a href="/pkg/text/template/">text/template</a></dt>
+ <dd>
+ <p><!-- CL 38420 -->
+ The handling of empty blocks, which was broken by a Go 1.8
+ change that made the result dependent on the order of templates,
+ has been fixed, restoring the old Go 1.7 behavior.
+ </p>
+
+</dl><!-- text/template -->
+
+<dl id="time"><dt><a href="/pkg/time/">time</a></dt>
+ <dd>
+ <p><!-- CL 36615 -->
+ The new methods
+ <a href="/pkg/time/#Duration.Round"><code>Duration.Round</code></a>
+ and
+ <a href="/pkg/time/#Duration.Truncate"><code>Duration.Truncate</code></a>
+ handle rounding and truncating durations to multiples of a given duration.
+ </p>
+
+ <p><!-- CL 35710 -->
+ Retrieving the time and sleeping now work correctly under Wine.
+ </p>
+
+ <p>
+ If a <code>Time</code> value has a monotonic clock reading, its
+ string representation (as returned by <code>String</code>) now includes a
+ final field <code>"m=±value"</code>, where <code>value</code> is the
+ monotonic clock reading formatted as a decimal number of seconds.
+ </p>
+
+ <p><!-- CL 44832 -->
+ The included <code>tzdata</code> timezone database has been
+ updated to version 2017b. As always, it is only used if the
+ system does not already have the database available.
+ </p>
+
+</dl><!-- time -->
diff --git a/doc/go_faq.html b/doc/go_faq.html
index 3006b3d..f8322ef 100644
--- a/doc/go_faq.html
+++ b/doc/go_faq.html
@@ -1140,7 +1140,7 @@
</p>
<p>
-The Go 1.5 release includes an experimental facility to the
+The Go 1.5 release added a facility to the
<a href="https://golang.org/cmd/go">go</a> command
that makes it easier to manage external dependencies by "vendoring"
them into a special directory near the package that depends upon them.
@@ -1148,6 +1148,13 @@
document</a> for details.
</p>
+<p>
+Work is underway on an experimental package management tool,
+<a href="https://github.com/golang/dep"><code>dep</code></a>, to learn
+more about how tooling can help package management. More information can be found in
+<a href="https://github.com/golang/dep/blob/master/FAQ.md">the <code>dep</code> FAQ</a>.
+</p>
+
<h2 id="Pointers">Pointers and Allocation</h2>
<h3 id="pass_by_value">
diff --git a/doc/go_spec.html b/doc/go_spec.html
index 5872eef..6642869 100644
--- a/doc/go_spec.html
+++ b/doc/go_spec.html
@@ -1,6 +1,6 @@
<!--{
"Title": "The Go Programming Language Specification",
- "Subtitle": "Version of November 18, 2016",
+ "Subtitle": "Version of June 28, 2017",
"Path": "/ref/spec"
}-->
@@ -154,7 +154,7 @@
<p>
Tokens form the vocabulary of the Go language.
There are four classes: <i>identifiers</i>, <i>keywords</i>, <i>operators
-and delimiters</i>, and <i>literals</i>. <i>White space</i>, formed from
+and punctuation</i>, and <i>literals</i>. <i>White space</i>, formed from
spaces (U+0020), horizontal tabs (U+0009),
carriage returns (U+000D), and newlines (U+000A),
is ignored except as it separates tokens
@@ -197,7 +197,7 @@
<code>return</code>
</li>
- <li>one of the <a href="#Operators_and_Delimiters">operators and delimiters</a>
+ <li>one of the <a href="#Operators_and_punctuation">operators and punctuation</a>
<code>++</code>,
<code>--</code>,
<code>)</code>,
@@ -254,10 +254,11 @@
continue for import return var
</pre>
-<h3 id="Operators_and_Delimiters">Operators and Delimiters</h3>
+<h3 id="Operators_and_punctuation">Operators and punctuation</h3>
<p>
-The following character sequences represent <a href="#Operators">operators</a>, delimiters, and other special tokens:
+The following character sequences represent <a href="#Operators">operators</a>
+(including <a href="#assign_op">assignment operators</a>) and punctuation:
</p>
<pre class="grammar">
+ & += &= && == != ( )
@@ -685,11 +686,9 @@
<h2 id="Types">Types</h2>
<p>
-A type determines the set of values and operations specific to values of that
-type. Types may be <i>named</i> or <i>unnamed</i>. Named types are specified
-by a (possibly <a href="#Qualified_identifiers">qualified</a>)
-<a href="#Type_declarations"><i>type name</i></a>; unnamed types are specified
-using a <i>type literal</i>, which composes a new type from existing types.
+A type determines a set of values together with operations and methods specific
+to those values. A type may be denoted by a <i>type name</i>, if it has one,
+or specified using a <i>type literal</i>, which composes a type from existing types.
</p>
<pre class="ebnf">
@@ -702,6 +701,7 @@
<p>
Named instances of the boolean, numeric, and string types are
<a href="#Predeclared_identifiers">predeclared</a>.
+Other named types are introduced with <a href="#Type_declarations">type declarations</a>.
<i>Composite types</i>—array, struct, pointer, function,
interface, slice, map, and channel types—may be constructed using
type literals.
@@ -717,16 +717,23 @@
</p>
<pre>
- type T1 string
- type T2 T1
- type T3 []T1
- type T4 T3
+type (
+ A1 = string
+ A2 = A1
+)
+
+type (
+ B1 string
+ B2 B1
+ B3 []B1
+ B4 B3
+)
</pre>
<p>
-The underlying type of <code>string</code>, <code>T1</code>, and <code>T2</code>
-is <code>string</code>. The underlying type of <code>[]T1</code>, <code>T3</code>,
-and <code>T4</code> is <code>[]T1</code>.
+The underlying type of <code>string</code>, <code>A1</code>, <code>A2</code>, <code>B1</code>,
+and <code>B2</code> is <code>string</code>.
+The underlying type of <code>[]B1</code>, <code>B3</code>, and <code>B4</code> is <code>[]B1</code>.
</p>
<h3 id="Method_sets">Method sets</h3>
@@ -738,7 +745,7 @@
The method set of the corresponding <a href="#Pointer_types">pointer type</a> <code>*T</code>
is the set of all methods declared with receiver <code>*T</code> or <code>T</code>
(that is, it also contains the method set of <code>T</code>).
-Further rules apply to structs containing anonymous fields, as described
+Further rules apply to structs containing embedded fields, as described
in the section on <a href="#Struct_types">struct types</a>.
Any other type has an empty method set.
In a method set, each method must have a
@@ -947,16 +954,16 @@
<p>
A struct is a sequence of named elements, called fields, each of which has a
name and a type. Field names may be specified explicitly (IdentifierList) or
-implicitly (AnonymousField).
+implicitly (EmbeddedField).
Within a struct, non-<a href="#Blank_identifier">blank</a> field names must
be <a href="#Uniqueness_of_identifiers">unique</a>.
</p>
<pre class="ebnf">
-StructType = "struct" "{" { FieldDecl ";" } "}" .
-FieldDecl = (IdentifierList Type | AnonymousField) [ Tag ] .
-AnonymousField = [ "*" ] TypeName .
-Tag = string_lit .
+StructType = "struct" "{" { FieldDecl ";" } "}" .
+FieldDecl = (IdentifierList Type | EmbeddedField) [ Tag ] .
+EmbeddedField = [ "*" ] TypeName .
+Tag = string_lit .
</pre>
<pre>
@@ -974,16 +981,15 @@
</pre>
<p>
-A field declared with a type but no explicit field name is an <i>anonymous field</i>,
-also called an <i>embedded</i> field or an embedding of the type in the struct.
-An embedded type must be specified as
+A field declared with a type but no explicit field name is called an <i>embedded field</i>.
+An embedded field must be specified as
a type name <code>T</code> or as a pointer to a non-interface type name <code>*T</code>,
and <code>T</code> itself may not be
a pointer type. The unqualified type name acts as the field name.
</p>
<pre>
-// A struct with four anonymous fields of type T1, *T2, P.T3 and *P.T4
+// A struct with four embedded fields of types T1, *T2, P.T3 and *P.T4
struct {
T1 // field name is T1
*T2 // field name is T2
@@ -1000,15 +1006,15 @@
<pre>
struct {
- T // conflicts with anonymous field *T and *P.T
- *T // conflicts with anonymous field T and *P.T
- *P.T // conflicts with anonymous field T and *T
+ T // conflicts with embedded field *T and *P.T
+ *T // conflicts with embedded field T and *P.T
+ *P.T // conflicts with embedded field T and *T
}
</pre>
<p>
A field or <a href="#Method_declarations">method</a> <code>f</code> of an
-anonymous field in a struct <code>x</code> is called <i>promoted</i> if
+embedded field in a struct <code>x</code> is called <i>promoted</i> if
<code>x.f</code> is a legal <a href="#Selectors">selector</a> that denotes
that field or method <code>f</code>.
</p>
@@ -1025,7 +1031,7 @@
</p>
<ul>
<li>
- If <code>S</code> contains an anonymous field <code>T</code>,
+ If <code>S</code> contains an embedded field <code>T</code>,
the <a href="#Method_sets">method sets</a> of <code>S</code>
and <code>*S</code> both include promoted methods with receiver
<code>T</code>. The method set of <code>*S</code> also
@@ -1033,7 +1039,7 @@
</li>
<li>
- If <code>S</code> contains an anonymous field <code>*T</code>,
+ If <code>S</code> contains an embedded field <code>*T</code>,
the method sets of <code>S</code> and <code>*S</code> both
include promoted methods with receiver <code>T</code> or
<code>*T</code>.
@@ -1418,11 +1424,10 @@
</p>
<p>
-Two <a href="#Types">named types</a> are identical if their type names originate in the same
-<a href="#Type_declarations">TypeSpec</a>.
-A named and an <a href="#Types">unnamed type</a> are always different. Two unnamed types are identical
-if the corresponding type literals are identical, that is, if they have the same
-literal structure and corresponding components have identical types. In detail:
+A <a href="#Type_definitions">defined type</a> is always different from any other type.
+Otherwise, two types are identical if their <a href="#Types">underlying</a> type literals are
+structurally equivalent; that is, they have the same literal structure and corresponding
+components have identical types. In detail:
</p>
<ul>
@@ -1434,8 +1439,8 @@
<li>Two struct types are identical if they have the same sequence of fields,
and if corresponding fields have the same names, and identical types,
and identical tags.
- Two anonymous fields are considered to have the same name. Lower-case field
- names from different packages are always different.</li>
+ <a href="#Exported_identifiers">Non-exported</a> field names from different
+ packages are always different.</li>
<li>Two pointer types are identical if they have identical base types.</li>
@@ -1445,8 +1450,9 @@
Parameter and result names are not required to match.</li>
<li>Two interface types are identical if they have the same set of methods
- with the same names and identical function types. Lower-case method names from
- different packages are always different. The order of the methods is irrelevant.</li>
+ with the same names and identical function types.
+ <a href="#Exported_identifiers">Non-exported</a> method names from different
+ packages are always different. The order of the methods is irrelevant.</li>
<li>Two map types are identical if they have identical key and value types.</li>
@@ -1460,13 +1466,24 @@
<pre>
type (
- T0 []string
- T1 []string
- T2 struct{ a, b int }
- T3 struct{ a, c int }
- T4 func(int, float64) *T0
- T5 func(x int, y float64) *[]string
+ A0 = []string
+ A1 = A0
+ A2 = struct{ a, b int }
+ A3 = int
+ A4 = func(A3, float64) *A0
+ A5 = func(x int, _ float64) *[]string
)
+
+type (
+ B0 A0
+ B1 []string
+ B2 struct{ a, b int }
+ B3 struct{ a, c int }
+ B4 func(int, float64) *B0
+ B5 func(x int, y float64) *A1
+)
+
+type C0 = B0
</pre>
<p>
@@ -1474,17 +1491,22 @@
</p>
<pre>
-T0 and T0
+A0, A1, and []string
+A2 and struct{ a, b int }
+A3 and int
+A4, func(int, float64) *[]string, and A5
+
+B0, B0, and C0
[]int and []int
struct{ a, b *T5 } and struct{ a, b *T5 }
-func(x int, y float64) *[]string and func(int, float64) (result *[]string)
+func(x int, y float64) *[]string, func(int, float64) (result *[]string), and A5
</pre>
<p>
-<code>T0</code> and <code>T1</code> are different because they are named types
-with distinct declarations; <code>func(int, float64) *T0</code> and
-<code>func(x int, y float64) *[]string</code> are different because <code>T0</code>
-is different from <code>[]string</code>.
+<code>B0</code> and <code>B1</code> are different because they are new types
+created by distinct <a href="#Type_definitions">type definitions</a>;
+<code>func(int, float64) *B0</code> and <code>func(x int, y float64) *[]string</code>
+are different because <code>B0</code> is different from <code>[]string</code>.
</p>
@@ -1502,7 +1524,7 @@
<li>
<code>x</code>'s type <code>V</code> and <code>T</code> have identical
<a href="#Types">underlying types</a> and at least one of <code>V</code>
-or <code>T</code> is not a <a href="#Types">named type</a>.
+or <code>T</code> is not a <a href="#Type_definitions">defined</a> type.
</li>
<li>
<code>T</code> is an interface type and
@@ -1511,7 +1533,7 @@
<li>
<code>x</code> is a bidirectional channel value, <code>T</code> is a channel type,
<code>x</code>'s type <code>V</code> and <code>T</code> have identical element types,
-and at least one of <code>V</code> or <code>T</code> is not a named type.
+and at least one of <code>V</code> or <code>T</code> is not a defined type.
</li>
<li>
<code>x</code> is the predeclared identifier <code>nil</code> and <code>T</code>
@@ -1840,23 +1862,60 @@
<h3 id="Type_declarations">Type declarations</h3>
<p>
-A type declaration binds an identifier, the <i>type name</i>, to a new type
-that has the same <a href="#Types">underlying type</a> as an existing type,
-and operations defined for the existing type are also defined for the new type.
-The new type is <a href="#Type_identity">different</a> from the existing type.
+A type declaration binds an identifier, the <i>type name</i>, to a <a href="#Types">type</a>.
+Type declarations come in two forms: alias declarations and type definitions.
+<p>
+
+<pre class="ebnf">
+TypeDecl = "type" ( TypeSpec | "(" { TypeSpec ";" } ")" ) .
+TypeSpec = AliasDecl | TypeDef .
+</pre>
+
+<h4 id="Alias_declarations">Alias declarations</h4>
+
+<p>
+An alias declaration binds an identifier to the given type.
</p>
<pre class="ebnf">
-TypeDecl = "type" ( TypeSpec | "(" { TypeSpec ";" } ")" ) .
-TypeSpec = identifier Type .
+AliasDecl = identifier "=" Type .
</pre>
-<pre>
-type IntArray [16]int
+<p>
+Within the <a href="#Declarations_and_scope">scope</a> of
+the identifier, it serves as an <i>alias</i> for the type.
+</p>
+<pre>
type (
- Point struct{ x, y float64 }
- Polar Point
+ nodeList = []*Node // nodeList and []*Node are identical types
+ Polar = polar // Polar and polar denote identical types
+)
+</pre>
+
+
+<h4 id="Type_definitions">Type definitions</h4>
+
+<p>
+A type definition creates a new, distinct type with the same
+<a href="#Types">underlying type</a> and operations as the given type,
+and binds an identifier to it.
+</p>
+
+<pre class="ebnf">
+TypeDef = identifier Type .
+</pre>
+
+<p>
+The new type is called a <i>defined type</i>.
+It is <a href="#Type_identity">different</a> from any other type,
+including the type it is created from.
+</p>
+
+<pre>
+type (
+ Point struct{ x, y float64 } // Point and struct{ x, y float64 } are different types
+ polar Point // polar and Point denote different types
)
type TreeNode struct {
@@ -1872,8 +1931,9 @@
</pre>
<p>
-The declared type does not inherit any <a href="#Method_declarations">methods</a>
-bound to the existing type, but the <a href="#Method_sets">method set</a>
+A defined type may have <a href="#Method_declarations">methods</a> associated with it.
+It does not inherit any methods bound to the given type,
+but the <a href="#Method_sets">method set</a>
of an interface type or of elements of a composite type remains unchanged:
</p>
@@ -1891,7 +1951,7 @@
type PtrMutex *Mutex
// The method set of *PrintableMutex contains the methods
-// Lock and Unlock bound to its anonymous field Mutex.
+// Lock and Unlock bound to its embedded field Mutex.
type PrintableMutex struct {
Mutex
}
@@ -1901,8 +1961,8 @@
</pre>
<p>
-A type declaration may be used to define a different boolean, numeric, or string
-type and attach methods to it:
+Type definitions may be used to define different boolean, numeric,
+or string types and associate methods with them:
</p>
<pre>
@@ -1924,8 +1984,8 @@
<h3 id="Variable_declarations">Variable declarations</h3>
<p>
-A variable declaration creates one or more variables, binds corresponding
-identifiers to them, and gives each a type and an initial value.
+A variable declaration creates one or more <a href="#Variables">variables</a>,
+binds corresponding identifiers to them, and gives each a type and an initial value.
</p>
<pre class="ebnf">
@@ -2083,8 +2143,8 @@
</p>
<pre class="ebnf">
-MethodDecl = "func" Receiver MethodName ( Function | Signature ) .
-Receiver = Parameters .
+MethodDecl = "func" Receiver MethodName ( Function | Signature ) .
+Receiver = Parameters .
</pre>
<p>
@@ -2093,7 +2153,7 @@
Its type must be of the form <code>T</code> or <code>*T</code> (possibly using
parentheses) where <code>T</code> is a type name. The type denoted by <code>T</code> is called
the receiver <i>base type</i>; it must not be a pointer or interface type and
-it must be declared in the same package as the method.
+it must be <a href="#Type_definitions">defined</a> in the same package as the method.
The method is said to be <i>bound</i> to the base type and the method name
is visible only within <a href="#Selectors">selectors</a> for type <code>T</code>
or <code>*T</code>.
@@ -2235,7 +2295,8 @@
an index for array and slice literals, and a key for map literals.
For map literals, all elements must have a key. It is an error
to specify multiple elements with the same field name or
-constant key value.
+constant key value. For non-constant map keys, see the section on
+<a href="#Order_of_evaluation">evaluation order</a>.
</p>
<p>
@@ -2492,13 +2553,13 @@
A selector <code>f</code> may denote a field or method <code>f</code> of
a type <code>T</code>, or it may refer
to a field or method <code>f</code> of a nested
-<a href="#Struct_types">anonymous field</a> of <code>T</code>.
-The number of anonymous fields traversed
+<a href="#Struct_types">embedded field</a> of <code>T</code>.
+The number of embedded fields traversed
to reach <code>f</code> is called its <i>depth</i> in <code>T</code>.
The depth of a field or method <code>f</code>
declared in <code>T</code> is zero.
The depth of a field or method <code>f</code> declared in
-an anonymous field <code>A</code> in <code>T</code> is the
+an embedded field <code>A</code> in <code>T</code> is the
depth of <code>f</code> in <code>A</code> plus one.
</p>
@@ -3323,7 +3384,7 @@
<p>
The right operand in a shift expression must have unsigned integer type
-or be an untyped constant that can be converted to unsigned integer type.
+or be an untyped constant representable by a value of type <code>uint</code>.
If the left operand of a non-constant shift expression is an untyped constant,
it is first converted to the type it would assume if the shift expression were
replaced by its left operand alone.
@@ -3521,6 +3582,33 @@
occurs is implementation-specific.
</p>
+<p>
+An implementation may combine multiple floating-point operations into a single
+fused operation, possibly across statements, and produce a result that differs
+from the value obtained by executing and rounding the instructions individually.
+A floating-point type <a href="#Conversions">conversion</a> explicitly rounds to
+the precision of the target type, preventing fusion that would discard that rounding.
+</p>
+
+<p>
+For instance, some architectures provide a "fused multiply and add" (FMA) instruction
+that computes <code>x*y + z</code> without rounding the intermediate result <code>x*y</code>.
+These examples show when a Go implementation can use that instruction:
+</p>
+
+<pre>
+// FMA allowed for computing r, because x*y is not explicitly rounded:
+r = x*y + z
+r = z; r += x*y
+t = x*y; r = t + z
+*p = x*y; r = *p + z
+r = x*y + float64(z)
+
+// FMA disallowed for computing r, because it would omit rounding of x*y:
+r = float64(x*y) + z
+r = z; r += float64(x*y)
+t = float64(x*y); r = t + z
+</pre>
<h4 id="String_concatenation">String concatenation</h4>
@@ -3579,7 +3667,7 @@
</li>
<li>
- Floating point values are comparable and ordered,
+ Floating-point values are comparable and ordered,
as defined by the IEEE-754 standard.
</li>
@@ -3849,7 +3937,8 @@
</li>
<li>
ignoring struct tags (see below),
- <code>x</code>'s type and <code>T</code> are unnamed pointer types
+ <code>x</code>'s type and <code>T</code> are pointer types
+ that are not <a href="#Type_definitions">defined types</a>,
and their pointer base types have identical underlying types.
</li>
<li>
@@ -4434,8 +4523,8 @@
<p>
An <i>assignment operation</i> <code>x</code> <i>op</i><code>=</code>
-<code>y</code> where <i>op</i> is a binary arithmetic operation is equivalent
-to <code>x</code> <code>=</code> <code>x</code> <i>op</i>
+<code>y</code> where <i>op</i> is a binary <a href="#Arithmetic_operators">arithmetic operator</a>
+is equivalent to <code>x</code> <code>=</code> <code>x</code> <i>op</i>
<code>(y)</code> but evaluates <code>x</code>
only once. The <i>op</i><code>=</code> construct is a single token.
In assignment operations, both the left- and right-hand expression lists
@@ -4936,8 +5025,8 @@
<li>
The iteration order over maps is not specified
and is not guaranteed to be the same from one iteration to the next.
-If map entries that have not yet been reached are removed during iteration,
-the corresponding iteration values will not be produced. If map entries are
+If a map entry that has not yet been reached is removed during iteration,
+the corresponding iteration value will not be produced. If a map entry is
created during iteration, that entry may be produced during the iteration or
may be skipped. The choice may vary for each entry created and from one
iteration to the next.
@@ -5037,7 +5126,7 @@
<pre>
go Server()
-go func(ch chan<- bool) { for { sleep(10); ch <- true; }} (c)
+go func(ch chan<- bool) { for { sleep(10); ch <- true }} (c)
</pre>
@@ -5583,7 +5672,7 @@
make(T, n, m) slice slice of type T with length n and capacity m
make(T) map map of type T
-make(T, n) map map of type T with initial space for n elements
+make(T, n) map map of type T with initial space for approximately n elements
make(T) channel unbuffered channel of type T
make(T, n) channel buffered channel of type T, buffer size n
@@ -5606,9 +5695,15 @@
s := make([]int, 1<<63) // illegal: len(s) is not representable by a value of type int
s := make([]int, 10, 0) // illegal: len(s) > cap(s)
c := make(chan int, 10) // channel with a buffer size of 10
-m := make(map[string]int, 100) // map with initial space for 100 elements
+m := make(map[string]int, 100) // map with initial space for approximately 100 elements
</pre>
+<p>
+Calling <code>make</code> with a map type and size hint <code>n</code> will
+create a map with initial space to hold <code>n</code> map elements.
+The precise behavior is implementation-dependent.
+</p>
+
<h3 id="Appending_and_copying_slices">Appending to and copying slices</h3>
@@ -5870,6 +5965,11 @@
println like print but prints spaces between arguments and a newline at the end
</pre>
+<p>
+Implementation restriction: <code>print</code> and <code>println</code> need not
+accept arbitrary argument types, but printing of boolean, numeric, and string
+<a href="#Types">types</a> must be supported.
+</p>
<h2 id="Packages">Packages</h2>
@@ -6331,7 +6431,7 @@
A <code>Pointer</code> is a <a href="#Pointer_types">pointer type</a> but a <code>Pointer</code>
value may not be <a href="#Address_operators">dereferenced</a>.
Any pointer or value of <a href="#Types">underlying type</a> <code>uintptr</code> can be converted to
-a <code>Pointer</code> type and vice versa.
+a type of underlying type <code>Pointer</code> and vice versa.
The effect of converting between <code>Pointer</code> and <code>uintptr</code> is implementation-defined.
</p>
@@ -6409,7 +6509,7 @@
</li>
<li>For a variable <code>x</code> of array type: <code>unsafe.Alignof(x)</code> is the same as
- <code>unsafe.Alignof(x[0])</code>, but at least 1.
+ the alignment of a variable of the array's element type.
</li>
</ol>
diff --git a/doc/help.html b/doc/help.html
index 62d9a4a..057d752 100644
--- a/doc/help.html
+++ b/doc/help.html
@@ -59,6 +59,12 @@
for Go news and discussion.
</p>
+<h3 id="gotime"><a href="https://changelog.com/gotime">Go Time Podcast</a></h3>
+<p>
+The <a href="https://changelog.com/gotime">Go Time podcast</a> is a panel of Go experts and special guests
+discussing the Go programming language, the community, and everything in between.
+</p>
+
<h2 id="community">Community resources</h2>
<h3 id="go_user_groups"><a href="/wiki/GoUserGroups">Go User Groups</a></h3>
diff --git a/doc/install-source.html b/doc/install-source.html
index 45c5bbb..5d732b0 100644
--- a/doc/install-source.html
+++ b/doc/install-source.html
@@ -143,7 +143,7 @@
<p>
To build a bootstrap tool chain from source, use
either the git branch <code>release-branch.go1.4</code> or
-<a href="https://storage.googleapis.com/golang/go1.4-bootstrap-20161024.tar.gz">go1.4-bootstrap-20161024.tar.gz</a>,
+<a href="https://storage.googleapis.com/golang/go1.4-bootstrap-20170531.tar.gz">go1.4-bootstrap-20170531.tar.gz</a>,
which contains the Go 1.4 source code plus accumulated fixes
to keep the tools running on newer operating systems.
(Go 1.4 was the last distribution in which the tool chain was written in C.)
@@ -221,7 +221,7 @@
Change to the directory that will be its parent
and make sure the <code>go</code> directory does not exist.
Then clone the repository and check out the latest release tag
-(<code class="versionTag">go1.8</code>, for example):</p>
+(<code class="versionTag">go1.8.1</code>, for example):</p>
<pre>
$ git clone https://go.googlesource.com/go
@@ -409,7 +409,7 @@
<a href="//groups.google.com/group/golang-announce">golang-announce</a>
mailing list.
Each announcement mentions the latest release tag, for instance,
-<code class="versionTag">go1.8</code>.
+<code class="versionTag">go1.8.1</code>.
</p>
<p>
diff --git a/doc/install.html b/doc/install.html
index 6bff75c..7f32f68 100644
--- a/doc/install.html
+++ b/doc/install.html
@@ -33,7 +33,7 @@
<h2 id="requirements">System requirements</h2>
<p>
-Go binary distributions are available for these supported operating systems and architectures.
+Go <a href="https://golang.org/dl/">binary distributions</a> are available for these supported operating systems and architectures.
Please ensure your system meets these requirements before proceeding.
If your OS or architecture is not on the list, you may be able to
<a href="/doc/install/source">install from source</a> or
@@ -47,10 +47,10 @@
<th align="center">Notes</th>
</tr>
<tr><td colspan="3"><hr></td></tr>
-<tr><td>FreeBSD 8-STABLE or later</td> <td>amd64, 386</td> <td>Debian GNU/kFreeBSD not supported</td></tr>
-<tr><td>Linux 2.6.23 or later with glibc</td> <td>amd64, 386, arm, s390x, ppc64le</td> <td>CentOS/RHEL 5.x not supported</td></tr>
-<tr><td>Mac OS X 10.8 or later</td> <td>amd64</td> <td>use the clang or gcc<sup>†</sup> that comes with Xcode<sup>‡</sup> for <code>cgo</code> support</td></tr>
-<tr><td>Windows XP or later</td> <td>amd64, 386</td> <td>use MinGW gcc<sup>†</sup>. No need for cygwin or msys.</td></tr>
+<tr><td>FreeBSD 9.3 or later</td> <td>amd64, 386</td> <td>Debian GNU/kFreeBSD not supported</td></tr>
+<tr valign='top'><td>Linux 2.6.23 or later with glibc</td> <td>amd64, 386, arm, arm64,<br>s390x, ppc64le</td> <td>CentOS/RHEL 5.x not supported.<br>Install from source for other libc.</td></tr>
+<tr><td>macOS 10.8 or later</td> <td>amd64</td> <td>use the clang or gcc<sup>†</sup> that comes with Xcode<sup>‡</sup> for <code>cgo</code> support</td></tr>
+<tr><td>Windows XP SP2 or later</td> <td>amd64, 386</td> <td>use MinGW gcc<sup>†</sup>. No need for cygwin or msys.</td></tr>
</table>
<p>
@@ -222,8 +222,7 @@
Create your <a href="code.html#Workspaces">workspace</a> directory,
<code class="testUnix">$HOME/go</code><code class="testWindows">%USERPROFILE%\go</code>.
(If you'd like to use a different directory,
-you will need to set the <code>GOPATH</code> environment variable;
-see <a href="code.html#Workspaces">How to Write Go Code</a> for details.)
+you will need to <a href="https://golang.org/wiki/SettingGOPATH">set the <code>GOPATH</code> environment variable</a>.)
</p>
<p>
diff --git a/doc/security.html b/doc/security.html
index 5911586..0d8b5ee 100644
--- a/doc/security.html
+++ b/doc/security.html
@@ -20,7 +20,7 @@
Your email will be acknowledged within 24 hours, and you'll receive a more
detailed response to your email within 72 hours indicating the next steps in
handling your report.
-If you would like, you can encrypt your report using our PGP key (listed below).
+For critical problems, you can encrypt your report using our PGP key (listed below).
</p>
<p>
@@ -118,6 +118,12 @@
<h3>PGP Key for <a href="mailto:security@golang.org">security@golang.org</a></h3>
+<p>
+We accept PGP-encrypted email, but the majority of the security team
+are not regular PGP users so it's somewhat inconvenient. Please only
+use PGP for critical security reports.
+</p>
+
<pre>
-----BEGIN PGP PUBLIC KEY BLOCK-----
Comment: GPGTools - https://gpgtools.org
