Crates.io | displaydoc-watt |
lib.rs | displaydoc-watt |
version | 0.1.0 |
source | src |
created_at | 2019-11-21 06:13:14.613503 |
updated_at | 2019-11-21 06:13:14.613503 |
description | A derive macro for implementing the display Trait via a doc comment and string interpolation |
homepage | https://github.com/yaahc/displaydoc |
repository | https://github.com/yaahc/displaydoc |
max_upload_size | |
id | 183149 |
size | 2,751,000 |
From<docs>
This library provides a convenient derive macro for the standard library's
core::fmt::Display
trait.
[dependencies]
displaydoc-watt = "0.1"
Compiler support: requires rustc 1.34+
use displaydoc_watt::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,
}
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)
Is this crate no_std
compatible?
displaydoc
crate does support no_std but I have not yet figured out how to make that work when the proc macro is compiled to wasm.Does this crate work with Path
and PathBuf
via the Display
trait?
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!