-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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: does not understand multiple keys in key:value pair in struct tag #43083
Comments
Also CC @timothy-king. |
Hm, I'm surprised that the feature was merged into master without teaching vet about it. |
@ianlancetaylor has offered to take a look, so I'll update the issue status to make that more visible. |
Sent https://golang.org/cl/277092 but it needs reviewers. |
Change https://golang.org/cl/277092 mentions this issue: |
@ianlancetaylor I can review this. |
This issue was closed because CL 277092 had a Re-opening to update the vendored copy of golang.org/x/tools in the standard library to pull in that change. |
Thanks. |
Change https://golang.org/cl/277076 mentions this issue: |
As of Go 1.16 the reflect package now supports multiple keys per tag. For golang/go#40281 Fixes golang/go#43083 Change-Id: I55cdc35c857a5e73dc009c2842d7bd83c63d7712 Reviewed-on: https://go-review.googlesource.com/c/tools/+/277092 Trust: Ian Lance Taylor <iant@golang.org> Run-TryBot: Ian Lance Taylor <iant@golang.org> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Tim King <taking@google.com>
Change https://golang.org/cl/281973 mentions this issue: |
This reverts CL 277092. Proposal golang/go#40281 was initially accepted, then declined. Stop accepting the new, now once again invalid, format. For golang/go#40281 For golang/go#43083 For golang/go#43226 Change-Id: Ida97263048f3a048f904a844f577d8353e3a1afa Reviewed-on: https://go-review.googlesource.com/c/tools/+/281973 Trust: Ian Lance Taylor <iant@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
Change https://golang.org/cl/282412 mentions this issue: |
Note: proposal #40281 was declined after all, so this change was rolled back. |
In particular bring in CL 201973, which reverts support for multiple keys in a struct tag. For #40281 For #43083 For #43226 Change-Id: I66e76639cbbca55bdbff6956acdb0a97650fdd31 Reviewed-on: https://go-review.googlesource.com/c/go/+/282412 Trust: Ian Lance Taylor <iant@golang.org> Run-TryBot: Ian Lance Taylor <iant@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Emmanuel Odeke <emmanuel@orijtech.com>
This reverts CL 277092. Proposal golang/go#40281 was initially accepted, then declined. Stop accepting the new, now once again invalid, format. For golang/go#40281 For golang/go#43083 For golang/go#43226 Change-Id: Ida97263048f3a048f904a844f577d8353e3a1afa Reviewed-on: https://go-review.googlesource.com/c/tools/+/281973 Trust: Ian Lance Taylor <iant@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
No error (because this example is taken from #40281 (comment))
What did you see instead?
Marking as a release-blocker because I believe it to be one.
Despite raising this issue, I share the concerns raised by @rogpeppe in #40281 (comment).
cc @rsc @mvdan @ianlancetaylor
The text was updated successfully, but these errors were encountered: