-
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
cmd/vet: update for new number formats [1.13 backport] #39287
Comments
Approving for 1.14 (#39288) and 1.13 (this issue). This is a serious problem affecting valid Go code with no workaround. |
I've described the mechanics to perform this backport in full detail in #29986 (comment). For the 1.13 backport, we need to:
|
Change https://golang.org/cl/237942 mentions this issue: |
Change https://golang.org/cl/237945 mentions this issue: |
Change https://golang.org/cl/237944 mentions this issue: |
Closed by merging 03eb5928a63b2227d996a7cc2ef45de5f335189e to release-branch.go1.13. |
…oat/complex types These verbs are supported as of Go 1.13. Updates golang/go#34993. For golang/go#39287. Change-Id: Ib7892e45b51073e3771bebb652a8fe3a1c6ae3c6 Reviewed-on: https://go-review.googlesource.com/c/tools/+/202041 Run-TryBot: Caleb Spare <[email protected]> Reviewed-by: Alan Donovan <[email protected]> (cherry picked from commit 04252ec) Reviewed-on: https://go-review.googlesource.com/c/tools/+/237942 Run-TryBot: Dmitri Shuralyov <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]>
Adding the `#` to a `b` flag is allowed and adds a leading `0b` to the output. For golang/go#39287. Change-Id: I421891f9478d1aaff2585455f38b3aa50e8277ab GitHub-Last-Rev: 016896a GitHub-Pull-Request: #182 Reviewed-on: https://go-review.googlesource.com/c/tools/+/203798 Reviewed-by: Erik Dubbelboer <[email protected]> Reviewed-by: Michael Matloob <[email protected]> Run-TryBot: Michael Matloob <[email protected]> Reviewed-on: https://go-review.googlesource.com/c/tools/+/237944 Run-TryBot: Dmitri Shuralyov <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]>
… strings %O is supported since Go 1.13. See golang.org/design/19308-number-literals for the background. Support for %O has been added by copying and adapting the %o implementation. Updates golang/go#29986. For golang/go#39287. Change-Id: Ic49d3cc8d9aefcc0ecbfcfe5ebf206e6f951d413 Reviewed-on: https://go-review.googlesource.com/c/tools/+/235100 Run-TryBot: Ian Lance Taylor <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]> Reviewed-on: https://go-review.googlesource.com/c/tools/+/237945 Run-TryBot: Dmitri Shuralyov <[email protected]>
Reopening for re-vendor (the last step of #39287 (comment)). |
Closed by merging 991d59a616deaaf84d86e0819e386431a7a31b87 to release-branch.go1.13. |
Closed by merging f7130111797081f96423344c9f062b15df555902 to release-branch.go1.13. |
Change https://golang.org/cl/238018 mentions this issue: |
…0615191743-991d59a616de This teaches vet to recognize the new formats %#b and %O on integers, %x on float/complex. They have been supported since the 1.13 release, but vet would warn about it. Also update cmd/vet testdata accordingly, as was done in CL 202083. Fixes #39287. For #29986. Change-Id: Ia7817ee60ae6beac32cc402c0c68afa917e4ef0f Reviewed-on: https://go-review.googlesource.com/c/go/+/238018 Run-TryBot: Dmitri Shuralyov <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]>
Fixed by merging 206ee87 to |
@ianlancetaylor requested issue #29986 to be considered for backport to the next 1.13 minor release.
The text was updated successfully, but these errors were encountered: