increase compatibility with json.Number to avoid accuracy loss of int#2
Open
zcs-seu wants to merge 5 commits intocaibirdme:masterfrom
Open
increase compatibility with json.Number to avoid accuracy loss of int#2zcs-seu wants to merge 5 commits intocaibirdme:masterfrom
zcs-seu wants to merge 5 commits intocaibirdme:masterfrom
Conversation
added 5 commits
December 10, 2018 17:32
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Using encoding/json to marshal/unmarshal a map may cause accuracy loss of int. In terms of this condition, we can use json.Number to avoid. Now I update yql by adding compatibility with json.Number