Adapters between minicbor and other crates such as heapless and cboritem
Find a file
chrysn f7a03c16db
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
Update heapless to 0.9 and release 0.0.8
Reviewed-on: #12
2025-10-09 16:51:18 +02:00
src heapless: Enable writing to aribtrarily backed Vec-ishs 2025-10-09 16:25:49 +02:00
.gitignore Initial checkin 2024-12-05 14:03:20 +01:00
.woodpecker.yml CI: Use doc2readme image 2025-10-09 15:39:48 +02:00
Cargo.lock Release v0.0.8 2025-10-09 16:35:43 +02:00
Cargo.toml Release v0.0.8 2025-10-09 16:35:43 +02:00
README.md Update minicbor to 2.0 and embedded-io to 0.7 2025-10-09 15:30:04 +02:00

minicbor-adapters License: MIT OR Apache-2.0 minicbor-adapters on crates.io minicbor-adapters on docs.rs Source Code Repository

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.