-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
json.%
raises Defect
for uint64
#17383
Comments
timotheecour
added a commit
to timotheecour/Nim
that referenced
this issue
Mar 15, 2021
… with uint|uint64
timotheecour
added a commit
to timotheecour/Nim
that referenced
this issue
Mar 15, 2021
… with uint|uint64
timotheecour
added a commit
to timotheecour/Nim
that referenced
this issue
Mar 15, 2021
… with uint|uint64
see #17389 |
timotheecour
added a commit
to timotheecour/Nim
that referenced
this issue
Mar 16, 2021
… with uint|uint64
Araq
pushed a commit
that referenced
this issue
Mar 16, 2021
narimiran
pushed a commit
that referenced
this issue
Mar 18, 2021
narimiran
pushed a commit
that referenced
this issue
Mar 18, 2021
narimiran
pushed a commit
that referenced
this issue
Mar 19, 2021
ringabout
pushed a commit
to ringabout/Nim
that referenced
this issue
Mar 22, 2021
… with uint|uint64 (nim-lang#17389) [backport:1.2] * fix nim-lang#17383: json.%,to and jsonutils.formJson,toJson now works with uint|uint64 * fixup * fix for js
ardek66
pushed a commit
to ardek66/Nim
that referenced
this issue
Mar 26, 2021
… with uint|uint64 (nim-lang#17389) [backport:1.2] * fix nim-lang#17383: json.%,to and jsonutils.formJson,toJson now works with uint|uint64 * fixup * fix for js
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Nim/lib/pure/json.nim
Line 315 in 51a04a3
converting a
uint64
to aJsonNode
raises aDefect
on values outside theBiggestInt
range, defeating the purpose of using this overload to begin with - to resolve, one would either deprecate / remove the overload or output a string instead - the latter would require parsing strings as well in the opposite direction.The text was updated successfully, but these errors were encountered: