#ascii #debug #string

byte_string

Wrapper types for outputting byte strings (b”Hello”) using the Debug ({:?}) format

1 stable release

Uses old Rust 2015

1.0.0 Sep 26, 2016

#760 in Rust patterns

Download history 326/week @ 2021-01-08 284/week @ 2021-01-15 340/week @ 2021-01-22 399/week @ 2021-01-29 333/week @ 2021-02-05 390/week @ 2021-02-12 339/week @ 2021-02-19 383/week @ 2021-02-26 468/week @ 2021-03-05 309/week @ 2021-03-12 317/week @ 2021-03-19 465/week @ 2021-03-26 264/week @ 2021-04-02 466/week @ 2021-04-09 400/week @ 2021-04-16 316/week @ 2021-04-23

1,502 downloads per month
Used in 7 crates (6 directly)

MIT/Apache

15KB
333 lines

byte_string Build Status

The byte_string crate provides two types: ByteStr and ByteString. Both types provide a Debug implementation that outputs the slice using the Rust byte string syntax. ByteStr wraps a byte slice ([u8]). ByteString wraps a vector of bytes (Vec<u8>).

For example:

extern crate byte_string;

use byte_string::ByteStr;

fn main() {
    let s = b"Hello, world!";
    let bs = ByteStr::new(s);
    assert_eq!(format!("{:?}", bs), "b\"Hello, world!\"");
}

ByteStr is an unsized type, as [u8] is. ByteStr::new() returns a &ByteStr and ByteStr::new_mut() returns a &mut ByteStr.

ByteStr and ByteString are meant to be used as an implementation detail. You should generally avoid exposing a ByteStr or a ByteString as part of a struct or enum; prefer exposing the underlying slice or vector instead. However, ByteStr and ByteString implement many traits, including derivable traits, which makes them suitable for use as a private member of a struct or enum.

License

byte_string is licensed under the terms of both the MIT license and the Apache License, version 2.0.

No runtime deps