#string #debugging #byte #ascii #hello #byte-slice #format

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

#1467 in Text processing

Download history 4151/week @ 2024-01-03 4137/week @ 2024-01-10 4058/week @ 2024-01-17 4899/week @ 2024-01-24 9096/week @ 2024-01-31 9835/week @ 2024-02-07 9424/week @ 2024-02-14 8008/week @ 2024-02-21 9669/week @ 2024-02-28 12023/week @ 2024-03-06 11841/week @ 2024-03-13 13651/week @ 2024-03-20 10381/week @ 2024-03-27 10832/week @ 2024-04-03 11061/week @ 2024-04-10 8516/week @ 2024-04-17

42,737 downloads per month
Used in 10 crates (8 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