Skip to content
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

cmd/vet: possible bug in code #15883

dlsniper opened this issue May 29, 2016 · 4 comments


None yet
5 participants
Copy link

commented May 29, 2016

  1. What version of Go are you using (go version)? 1739657
  2. What operating system and processor architecture are you using (go env)? not important
  3. What did you do?

Looking at

indexPending := false
it seems that there's a new variable initialized called indexPending. I believe the correct code should remove that and change the code at
if !indexPending && !state.parseIndex() {
to check for state.indexPending instead of indexPending as it does right now.

  1. What did you expect to see?
    Not sure what that will impact, hopefully nothing.
  2. What did you see instead?
    Either a possible leftover or a possible bug / inconsistency.

This comment has been minimized.

Copy link
Contributor Author

commented May 30, 2016

I will send the CL soon.


This comment has been minimized.

Copy link

commented May 30, 2016

CL mentions this issue.

@quentinmit quentinmit added this to the Unplanned milestone Jun 17, 2016


This comment has been minimized.

Copy link

commented Jun 23, 2016

FYI, The bug will be resolved in #15884 . See the CL, so the issue may be closed now.


This comment has been minimized.

Copy link

commented Jul 18, 2017

Closing, then.

@ALTree ALTree closed this Jul 18, 2017

@golang golang locked and limited conversation to collaborators Jul 18, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.