Use go 1.19 #2708
Merged
Use go 1.19 #2708
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
opudrovs
approved these changes
Sep 6, 2022
ozamosi
force-pushed
the
go-1.19
branch
2 times, most recently
from
631cf2e
to
cf36ad7
Compare
The change mostly consists of a bunch of `//` having been inserted by the upgraded `go fmt`, and remove ioutil all over. For compatibility's sake, I've left go.mod still supporting 1.18, but all lint rules and the like are now using 1.19. This resolves #2681.
This was referenced Sep 27, 2022
Merged
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The change mostly consists of a bunch of
//having been inserted bythe upgraded
go fmt, and remove ioutil all over.For compatibility's sake, I've left go.mod still supporting 1.18, but
all lint rules and the like are now using 1.19.
This resolves #2681.