Skip to content

x/tools/cmd/vet: not always warning about capturing range variable in function literal #8732

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
reusee opened this issue Sep 15, 2014 · 3 comments

Comments

@reusee
Copy link

reusee commented Sep 15, 2014

What does 'go version' print?
go version devel +d0331dfbc053 Fri Sep 12 16:35:40 2014 -0700 linux/amd64

What steps reproduce the problem?
go tool vet [program]

What happened?
http://play.golang.org/p/tB3tpqV1yT this warns,
http://play.golang.org/p/6HYeRqt_pw this doesn't,
http://play.golang.org/p/ULAplewjBO and this warns.
@griesemer
Copy link
Contributor

Comment 1:

Labels changed: added repo-tools.

Owner changed to @robpike.

@robpike
Copy link
Contributor

robpike commented Oct 1, 2014

Comment 2:

Owner changed to @adg.

@reusee reusee added new labels Oct 1, 2014
@bradfitz bradfitz removed the new label Dec 18, 2014
@rsc rsc added this to the Unplanned milestone Apr 10, 2015
@rsc rsc changed the title cmd/vet: not always warning about capturing range variable in function literal x/tools/cmd/vet: not always warning about capturing range variable in function literal Apr 14, 2015
@rsc rsc modified the milestones: Unreleased, Unplanned Apr 14, 2015
@rsc rsc removed the repo-tools label Apr 14, 2015
@adg
Copy link
Contributor

adg commented May 27, 2016

This is by design.

@adg adg closed this as completed May 27, 2016
@golang golang locked and limited conversation to collaborators May 27, 2017
@rsc rsc unassigned adg Jun 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants