log-to-defmt 0.1.0

A backend for log that emits through defmt
Documentation
  • Coverage
  • 100%
    2 out of 2 items documented0 out of 1 items with examples
  • Size
  • Source code size: 11.23 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 548.78 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 18s Average build duration of successful builds.
  • all releases: 18s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • chrysn/log-to-defmt
    0 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • chrysn

log-to-defmt

This is a logging adapter that acts as an implementation of the log crate and hands the rendered messages off to the defmt crate.

Using this is generally not recommended: Once the log infrastructure is pulled into a project, Rust's string formatting is brought in, avoiding which is a big part of the point of defmt.

However, this can be useful during development, when debugging a particular library (that optionally produces messages through log) on a platform for which a defmt output has already been established.

Maturity

The current implementation of this takes a huge amount of shortcuts: not only does it not convert log levels, it also hardwires some to the most verbose level, discards lots of information that would otherwise be available, and uses a fixed size buffer.

Future iterations of this crate are expected to address these on demand; for example, this could gain a build time configuration mechanism for the maximum expected length, or an alloc feature that renders the log messages to a Vec instead of a heapless::Vec before handing them off to defmt as a slice.

The crate will likely introduce such features (altering its behavior) without declaring breaking changes; users are advised to configure their error levels to match which messages they expect to see.

License: MIT OR Apache-2.0