#display #derive

macro displaydoc

A derive macro for implementing the display Trait via a doc comment and string interpolation

10 releases

0.2.1 Mar 26, 2021
0.2.0 Mar 17, 2021
0.1.7 Jul 18, 2020
0.1.6 May 3, 2020
0.1.4 Oct 18, 2019

#39 in Rust patterns

Download history 5514/week @ 2021-02-26 5681/week @ 2021-03-05 7299/week @ 2021-03-12 8798/week @ 2021-03-19 7749/week @ 2021-03-26 6960/week @ 2021-04-02 7631/week @ 2021-04-09 7587/week @ 2021-04-16 8065/week @ 2021-04-23 8791/week @ 2021-04-30 9568/week @ 2021-05-07 10566/week @ 2021-05-14 10140/week @ 2021-05-21 8557/week @ 2021-05-28 10348/week @ 2021-06-04 10776/week @ 2021-06-11

31,936 downloads per month
Used in 66 crates (34 directly)

MIT/Apache

20KB
358 lines

derive(Display) /// From<docs>

Latest Version Rust Documentation

This library provides a convenient derive macro for the standard library's core::fmt::Display trait.

[dependencies]
displaydoc = "0.2"

Compiler support: requires rustc 1.31+


Example

use std::io;
use displaydoc::Display;
use thiserror::Error;

#[derive(Display, Error, Debug)]
pub enum DataStoreError {
    /// data store disconnected
    Disconnect(#[source] io::Error),
    /// the data for key `{0}` is not available
    Redaction(String),
    /// invalid header (expected {expected:?}, found {found:?})
    InvalidHeader {
        expected: String,
        found: String,
    },
    /// unknown data store error
    Unknown,
}

Details

  • A Display impl is generated for your type if you provide doc comment messages on the struct or each variant of your enum, as shown above in the example.

    The messages support a shorthand for interpolating fields from the error.

    • /// {var}write!("{}", self.var)
    • /// {0}write!("{}", self.0)
    • /// {var:?}write!("{:?}", self.var)
    • /// {0:?}write!("{:?}", self.0)

FAQ

  1. Is this crate no_std compatible?

    • Yes! This crate implements the core::fmt::Display trait not the std::fmt::Display trait so it should work in std and no_std environments. Just add default-features = false.
  2. Does this crate work with Path and PathBuf via the Display trait?

    • Yuuup. This crate uses @dtolnay's autoref specialization technique to add a special trait for types to get the display impl, it then specializes for Path and PathBuf and when either of these types are found it calls self.display() to get a std::path::Display<'_> type which can be used with the Display format specifier!

License

Licensed under either of Apache License, Version 2.0 or MIT license at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this crate by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

Dependencies

~335–760KB
~19K SLoC