Is there any way to configure or modify the parsing such that Klaxon can handle `NaN` in input?

[robert-dodier]

The literal NaN is recognized by some JSON parsers as IEEE 754 not-a-number, but it appears that Klaxon doesn't. I looked at the source code and I wasn't able to find a flag to enable that.

Is there any way to tell Klaxon to recognize NaN in input?

Is there a simple way to supply some additional function or something to the parser to tell it how to handle NaN?

Thank you for any light you can shed on this problem.

[snej]

FYI, NaN is not valid JSON, so no conformant JSON generator should be producing it. (It’s valid in JSON5, though.)