-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
doc/go1.16: document vet changes for Go 1.16 #42895
Comments
@timothy-king has offered to take this. Thanks! |
Change https://golang.org/cl/274617 mentions this issue: |
We might also want to mention https://go-review.googlesource.com/c/tools/+/248686 (vet pass to check for invalid frame pointer usage). |
Actually, that change has not been vendored in from |
@randall77 I'm looking to pull in changes that are in scope for Go 1.16 in CL 275446 (which may end up being split into smaller commits, or otherwise changed not to pull everything in). That is to say, it should happen, but it's not guaranteed to. If it's important for it to be included in Go 1.16 beta 1, please file a separate issue for it and CC me on it. You can send a CL that updates just x/tools to resolve it. Edit: I see that it'll need a change in cmd/vet to start using the new |
Ok, I'll open a new issue and prepare some CLs. |
@dmitshur Can you cc me if framepointer is added to the release? |
@timothy-king Please see CL 276372 and CL 276373 that @randall77 just sent. |
As of filing this issue, the Go 1.16 draft release notes contained the following HTML:
Per golang.org/s/release, it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.
A sequence of steps to resolve this issue may be:
The text was updated successfully, but these errors were encountered: