This PR (HEAD:770502a) has been imported to Gerrit for code review.

Please visit Gerrit athttps://go-review.googlesource.com/c/go/+/725605.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account tolog in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking asDone in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click theblueReply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See theSending a change via GitHub andReviews sections of the Contribution Guide as well as theFAQ for details.

Message from Gopher Robot:

Patch Set 1:

(1 comment)

Please don’t reply on this GitHub thread. Visitgolang.org/cl/725605.
After addressing review feedback, remember topublish your drafts!

Message from Ian Lance Taylor:

Patch Set 1:

(1 comment)

Please don’t reply on this GitHub thread. Visitgolang.org/cl/725605.
After addressing review feedback, remember topublish your drafts!

This PR (HEAD:2eb154b) has been imported to Gerrit for code review.

Please visit Gerrit athttps://go-review.googlesource.com/c/go/+/725605.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account tolog in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking asDone in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click theblueReply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See theSending a change via GitHub andReviews sections of the Contribution Guide as well as theFAQ for details.

Message from sz dxasu:

Patch Set 2:

(2 comments)

Please don’t reply on this GitHub thread. Visitgolang.org/cl/725605.
After addressing review feedback, remember topublish your drafts!

Message from Damien Neil:

Patch Set 2:

(3 comments)

Please don’t reply on this GitHub thread. Visitgolang.org/cl/725605.
After addressing review feedback, remember topublish your drafts!

Message from Damien Neil:

Patch Set 2:

(1 comment)

Please don’t reply on this GitHub thread. Visitgolang.org/cl/725605.
After addressing review feedback, remember topublish your drafts!

This PR (HEAD:647cf55) has been imported to Gerrit for code review.

Please visit Gerrit athttps://go-review.googlesource.com/c/go/+/725605.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account tolog in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking asDone in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click theblueReply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See theSending a change via GitHub andReviews sections of the Contribution Guide as well as theFAQ for details.

Message from sz dxasu:

Patch Set 2:

(2 comments)

Please don’t reply on this GitHub thread. Visitgolang.org/cl/725605.
After addressing review feedback, remember topublish your drafts!