Message from Gerrit User 5976:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
Within the next week or so, a maintainer will review your change and provide
feedback. See https://golang.org/doc/contribute.html#review for more info and
tips to get your patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11, it means that this CL will be reviewed as part of the next development
cycle. See https://golang.org/s/release for more details.

Please don’t reply on this GitHub thread. Visit golang.org/cl/125275.
After addressing review feedback, remember to publish your drafts!

Message from Gerrit User 7435:

Patch Set 1:

What performance problem is solved by this CL? The change is unlikely to be accepted without a good reason.

Please don’t reply on this GitHub thread. Visit golang.org/cl/125275.
After addressing review feedback, remember to publish your drafts!

Message from Gerrit User 5065:

Patch Set 1: Code-Review-2

Yeah, sorry, this isn't something we want to accept.

We prefer defer unless there's a good performance reason and this code isn't hot so I don't see any reason to micro-optimize it.

Please don’t reply on this GitHub thread. Visit golang.org/cl/125275.
After addressing review feedback, remember to publish your drafts!

This PR is being closed because golang.org/cl/125275 has been abandoned.