cbor
cbor copied to clipboard
pyfisch
CBOR support for serde.
Fixes #187 Legacy enum format supported packed encoding pretty well but with the switch to new enum format there was a regression (#173). This commit fixes the new enum format...
The `unsealed_read_write` feature that lifts the seals off Read and Write is convenient now, but I have doubts it's ideal with respect to maintaining stable versions: A crate that depends...
https://cbor.io/spec.html states that [RFC-8949](https://www.rfc-editor.org/rfc/rfc8949.html) is a new edition of RFC-7049 that describes the _same_ format, but with more explanation of topics that had arisen since the first RFC. It would...
I briefly scanned through the code and I don’t believe this crate supports BigFloat as defined in RFC 8949 section 3.4.4. I believe rust-decimal is the most common crate implementing...
This PR adds support for `u128` and `i128` in accordance with [§2.4.2 of the CBOR spec](https://tools.ietf.org/html/rfc7049#section-2.4.2).
The program crashes when trying to serialize them, complaining i/u128 is not supported Serde itself already has support for that
CBOR knows these two types ([spec](https://www.rfc-editor.org/rfc/rfc8949.html#fpnoconttbl2)): - `0xf6` => `null` - `0xf7` => `undefined` Serde only knows `Null` afaik, or at least the `Value` enum doesn't have anything closer to...
https://github.com/pyfisch/cbor/blob/a218403a52e60c991313f429e4acc05cce81ce25/src/de.rs#L859 If I try to write an enum as e.g. `\xbf\x67variant\x65hello\xff` there's a somewhat confusing error: "invalid type: map, expected variant identifier" This is probably not common (I was just...
So I have a variant of an enum, `Contributor::Ip`, and an equivalent struct `IpContributor`. The struct round-trips through serialization and deserialization but the enum variant with just one field doesn't,...
