//! 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 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.
pub use WithOpaque;
pub use WriteToEmbeddedIo;
pub use WriteToHeapless;
pub use ;