Windel Bouwman
Windel Bouwman
Since there are more people willing to help, where does the development continue? Do we ditch all old code, and start over, or is there a gradual migration path?
In order to push this forward, it might make sense to start a rust-cbor organization, and add the people here https://github.com/rust-cbor
I also opened up a matrix chat room at `#rust-cbor:matrix.org`
Btw, I tried `serde_json`, and this crate works well with these lines: ```rust let txt = serde_json::to_string(&stuff1).unwrap(); let stuff2 = serde_json::from_str(&txt).unwrap(); ```
Any clue yet on how this should be fixed? I'm not into serde, so I do not yet grasp how it should work. Also, the issue is more about the...
I found a solution to this issue. The solution was to always visit the f64 variant, since the cbor encoding is smart, and tries to use a compact value as...
I added a field in the roundtrip test case with of type f32 to test this. Is there a sort of stress test for rountripping all serde types available?
Excuse me for the many commits, please squash merge if merging this work.
@pyfisch what do you think about this change? Is it good / bad? I had some second thoughts about the packing / unpacking logic of floating point values. I noticed...
@pickfire I do not understand what you mean. Is there a `f128` type? Then probably we need to use it as well.