-
Notifications
You must be signed in to change notification settings - Fork 64
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
Wait next RapidJSON release for fixes NaN encoding. #11
Comments
I thought this had been done already in 1f37cec (see "ad1d22e Fix #509 by checking Nan/Inf when writing a double") ? |
Yes it still result
|
Strange... BTW, I think it is needed to check the return |
It does not return |
Yes. I have asked GitHub support that recently some PR was merged but the commit was lost in the history. |
I have got one e-mail but the admin don't think there is problem. |
Updated and tested in commit 7918f5b. |
(Moved form #9 (comment))
NaN encoding, i.e. encode(0/0), is not throwing an error (nil + error message).
I expected so according to: Tencent/rapidjson#509
The text was updated successfully, but these errors were encountered: