minicbor-adapters 0.0.7

# minicbor-adapters ![License: MIT OR Apache-2.0](https://img.shields.io/badge/license-MIT%20OR%20Apache--2.0-blue) [![minicbor-adapters on crates.io](https://img.shields.io/crates/v/minicbor-adapters)](https://crates.io/crates/minicbor-adapters) [![minicbor-adapters on docs.rs](https://docs.rs/minicbor-adapters/badge.svg)](https://docs.rs/minicbor-adapters) [![Source Code Repository](https://img.shields.io/badge/Code-On%20Codeberg-blue?logo=Codeberg)](https://codeberg.org/chrysn/minicbor-adapters)

Adapters between [`minicbor`][__link0] 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 minicbor
itself or in the crate providing the type. As minicbor tries to keep its (even optional)
dependency count at a minimum, and other crates are more general-purpose than minicbor, 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 any of those crates has a breaking release, possibly multiple at the
same time.

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 was often the case with minicbor \< 1.0); nonetheless, this is currently not
done for reasons of simplicity.


 [__cargo_doc2readme_dependencies_info]: ggGkYW0CYXSEG_W_Gn_kaocAGwCcVPfenh7eGy6gYLEwyIe4G6-xw_FwcbpjYXKEG3DkhFfaDbMXG6jowVHzmFFgG7bgyJrojG4kG-Zq2Siv80TyYWSBgmhtaW5pY2JvcmUyLjEuMQ
 [__link0]: https://crates.io/crates/minicbor/2.1.1