David Tolnay
David Tolnay
``` rust #[serde(default="0.1")] pub n: f32 ``` There is an ambiguity when the field is of function type so we need to figure that out.
The documentation for [Serializer::serialize_struct](https://docs.rs/serde/1.0/serde/trait.Serializer.html#tymethod.serialize_struct) currently says: > `len` is the number of data fields that will be serialized. This implies that the count of skipped field is not to be...
Newer versions of Jackson are really helpful about giving you the full path to the thing that errored out. See if this is something we can do with minimal performance...
The current behavior of StreamDeserializer is that if it hits an error, that same error is returned in perpetuity which is typically not what you want. (If that _is_ what...
Currently the stream API looks like: ```rust impl where R: Read, { type Item = Result; fn next(&mut self) -> Option; } ``` There should be some way to pass...
It takes 750 ms to deserialize [these types](https://github.com/mitsuhiko/rust-sourcemap/blob/170f026fe34eac03275891a04254a8eb2bf84642/src/jsontypes.rs.in) while json.load in python takes 300 ms. Reported by @mitsuhiko in IRC.
Currently f32::NAN and f64::NAN get serialized as null but fail to deserialize back as NAN. cc @sfackler
Currently an invocation like `json!({ "x": 0, "y": 'y' as i8, "z": [] })` expands into: ```rust ::serde_json::Value::Object({ let mut object = ::serde_json::Map::new(); let _ = object.insert(...); let _ =...
It seems like a common situation to have a [large](https://github.com/serde-rs/json/issues/403) top-level array in a JSON file. ```rust [ {...}, {...}, {...}, ... ] ``` StreamDeserializer should expose a way to...
In the following string validation, the error message points to the close quote after "test123". It would be nicer to point to the opening quote instead. ```rust #[macro_use] extern crate...