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: report type and format specifier mismatch in Printf* #4404

Closed
mewmew opened this issue Nov 17, 2012 · 4 comments

Comments

Projects
None yet
4 participants
@mewmew
Copy link
Contributor

commented Nov 17, 2012

What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.
1. go vet http://play.golang.org/p/x7Ae55GiUA

What is the expected output?
Errors are displayed at runtime. These could be reported by "go vet" after
static analysis.

What do you see instead?
"go vet" reports no errors.

Which compiler are you using (5g, 6g, 8g, gccgo)?
6g

Which operating system are you using?
linux

Which version are you using?  (run 'go version')
go version devel +13d81e48dc90 Fri Nov 16 13:25:01 2012 -0800
@robpike

This comment has been minimized.

Copy link
Contributor

commented Nov 17, 2012

Comment 1:

Labels changed: added priority-later, removed priority-triage.

Owner changed to @robpike.

Status changed to Accepted.

@mewmew

This comment has been minimized.

Copy link
Contributor Author

commented Nov 18, 2012

Comment 2:

Initial work has been started on the following CR:
https://golang.org/cl/6853062/
@rsc

This comment has been minimized.

Copy link
Contributor

commented Dec 9, 2012

Comment 3:

If we do this, it should be done with the new type checker. That means it won't be done
for Go 1.1.

Labels changed: removed go1.1.

@robpike

This comment has been minimized.

Copy link
Contributor

commented Feb 23, 2013

Comment 4:

This issue was closed by revision 72b6daa.

Status changed to Fixed.

@mewmew mewmew added fixed labels Feb 23, 2013

@golang golang locked and limited conversation to collaborators Jun 24, 2016

This issue was closed.

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.