11 releases

0.5.4 Nov 16, 2023
0.5.2 Apr 13, 2023
0.5.1 Jan 26, 2023
0.5.0 Sep 27, 2022
0.1.0 Nov 12, 2020

#74 in Rust patterns

Download history 21114/week @ 2024-01-05 22160/week @ 2024-01-12 23620/week @ 2024-01-19 26954/week @ 2024-01-26 31289/week @ 2024-02-02 30799/week @ 2024-02-09 30408/week @ 2024-02-16 30779/week @ 2024-02-23 30084/week @ 2024-03-01 33358/week @ 2024-03-08 33329/week @ 2024-03-15 31186/week @ 2024-03-22 29643/week @ 2024-03-29 30438/week @ 2024-04-05 31374/week @ 2024-04-12 29398/week @ 2024-04-19

126,244 downloads per month
Used in 145 crates (19 directly)

Custom license

33KB
559 lines

writeable crates.io

writeable is a utility crate of the ICU4X project.

It includes Writeable, a core trait representing an object that can be written to a sink implementing std::fmt::Write. It is an alternative to std::fmt::Display with the addition of a function indicating the number of bytes to be written.

Writeable improves upon std::fmt::Display in two ways:

  1. More efficient, since the sink can pre-allocate bytes.
  2. Smaller code, since the format machinery can be short-circuited.

Examples

use std::fmt;
use writeable::assert_writeable_eq;
use writeable::LengthHint;
use writeable::Writeable;

struct WelcomeMessage<'s> {
    pub name: &'s str,
}

impl<'s> Writeable for WelcomeMessage<'s> {
    fn write_to<W: fmt::Write + ?Sized>(&self, sink: &mut W) -> fmt::Result {
        sink.write_str("Hello, ")?;
        sink.write_str(self.name)?;
        sink.write_char('!')?;
        Ok(())
    }

    fn writeable_length_hint(&self) -> LengthHint {
        // "Hello, " + '!' + length of name
        LengthHint::exact(8 + self.name.len())
    }
}

let message = WelcomeMessage { name: "Alice" };
assert_writeable_eq!(&message, "Hello, Alice!");

// Types implementing `Writeable` are recommended to also implement `fmt::Display`.
// This can be simply done by redirecting to the `Writeable` implementation:
writeable::impl_display_with_writeable!(WelcomeMessage<'_>);

More Information

For more information on development, authorship, contributing etc. please visit ICU4X home page.

No runtime deps