Currently f{32,64}::NAN, INFINITE and NEG_INFINITY (i.e. if !v.is_finite()) are all emitted like their ryu serializations. This is wrong and breaks JSON.
Instead, emit null, like serde_json does.
On deserialization, interpret null as NAN where f32 or f64 is expected. This isn't exactly what serde_json does (it errors out instead), but makes the round-trip closer and somewhat more robust. And many would claim that it is common to interpret a JSON null as NAN where a float is expected (from schema/context/protocol).
Currently
f{32,64}::NAN,INFINITEandNEG_INFINITY(i.e. if!v.is_finite()) are all emitted like theirryuserializations. This is wrong and breaks JSON. Instead, emitnull, likeserde_jsondoes. On deserialization, interpretnullasNANwheref32orf64is expected. This isn't exactly whatserde_jsondoes (it errors out instead), but makes the round-trip closer and somewhat more robust. And many would claim that it is common to interpret a JSONnullasNANwhere a float is expected (from schema/context/protocol).