Nathaniel McCallum

> The one case I want to make sure this _does_ address correctly, though, is feature unification. If you build something twice, once for the regular dependency and once for...

No idea. But I'd rather have one really good CBOR stack than multiple incomplete ones. Was there some defect or design considerations in ciborium that lead to an alternate implementation?

> There are two missing things in ciborium that prompted me to develop this crate > > 1. ciborium has not exposed the `Serializer` api for a long time https://github.com/enarx/ciborium/issues/18...

@quininer If this is the biggest blocker, I'm happy to help you implement it.

I submitted 4 pull requests today. This is almost exclusively on the "top" end of the current crate. This implies that the low-level work should be unimpacted by these changes....

This is just a note to everyone that there is now a new serde-enabled CBOR crate named [ciborium](https://crates.io/crates/ciborium) ([documentation here](https://docs.rs/ciborium/0.1.0/ciborium/)). This was built by the Enarx project which is actively...

> @npmccallum except for the no_std no alloc use case it seems The readme discusses a potential low level library which could target that case. I would merge patches for...

> It doesn't have `Serializer` and `Deserializer` which we can easily use for `serde_transcode`. It does, they're just private because I wasn't sure if anyone actually needed them. We can...

One decision I was on the fence about: `cbor!(null)` or `cbor!(Null)`. The first one is closer to JSON and matches other keywords like `true` and `false`. The second one is...

Const generics are now stable in 1.51.