minicbor-adapters

Adapters between minicbor and other crates

Some pairs of types don’t have a clear place to implement with minicbor: Due to the orphan rule, an implementation of minicbor’s traits for a type needs to be implemented either in minicobor itself or in the crate providing the type. As minicbor tries to keep its (even optional) dependency count at a minimum, and other crates can’t be expected to keep up with minicbor’s pace of releases, this crate provides thin wrapper types that provide the implementations.

Versioning

This crate has both minicbor and the related types as public dependencies. It will thus undergo a breaking change when minicbor updates, often lockstepping those to the latest version of the other crates.

Providing implementations for a larger matrix is generally feasilbe by depending on multiple versions of crates, and is sometimes maintainable when the breaking changes don’t affect the implementation (as is often the case with minicbor); nonetheless, this is currently not done for reasons of simplicity.