Minor changes necessary to run go test under 1.15
#32
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
In Go 1.15, converting from non-byte or -rune integer types directly to a string became a `go vet` warning, enabled by default when running `go test`. Goutils was using this conversion correctly, so mechanically wrapping an additional conversion to `rune` (as suggested by the Go 1.15 changelog) at the warning sites allows `go test` to run without errors on recent Go toolchains.
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.
In Go 1.15, converting from non-byte or -rune integer types directly to a string became a
go vetwarning, enabled by default when runninggo test. Goutils was using this conversion correctly, so mechanically wrapping an additional conversion torune(as suggested by the Go 1.15changelog) at the warning sites allows
go testto run without errors on recent Go toolchains.