Float `nan` values are generated in JSON

[PMunch]

Had an issue recently where NaN values from Nim got written to JSON as nan. According to the official JSON spec nan is not a valid value in JSON. Not quite sure what the actual behaviour here should be. I see that jq parses such JSON fine, but Nims parseJson fails.

[treeform]

NaN is not a valid number in json, so I will not parse it. If you are expecting to get NaNs some times you could make a parseHook and parse them yourself.

[PMunch]

As it should be, but this issue is about jsony creating nans when converting an object to a JSON string

[PMunch]

Here's a small reproduction:

import jsony

type m = object
  test: string
  field: float

echo m(test: "Hello world", field: Nan).toJson

which produces:

{"test":"Hello world","field":nan}

Notice how field in the JSON output has the illegal value of nan.

[pietroppeter]

For reference in Python there is an allow_nan parameters that allows to output nans (and infinity values). If set to False it would raise an error when serializing an non number value. https://docs.python.org/3/library/json.html#basic-usage

[treeform]

Sorry this is indeed a real issue.