You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling double-to-json_string on a double with no fractional component results in the dropping of both the trailing zero and the period (e.g. 1.0 is serialized as 1). So when that string is deserialized, the type is inferred as an int. I am not sure if this is the intended behavior of this function or not. This comment leads me to believe it is not. It seems that the use of %g is the cause of this behavior.
FWIW, you can find the full discussion we had about this issue in the flux-framework project here.
The text was updated successfully, but these errors were encountered:
Calling
double-to-json_string
on a double with no fractional component results in the dropping of both the trailing zero and the period (e.g.1.0
is serialized as1
). So when that string is deserialized, the type is inferred as an int. I am not sure if this is the intended behavior of this function or not. This comment leads me to believe it is not. It seems that the use of%g
is the cause of this behavior.FWIW, you can find the full discussion we had about this issue in the flux-framework project here.
The text was updated successfully, but these errors were encountered: