#debugging #ascii #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

#1792 in Text processing

Download history 14530/week @ 2024-12-12 11590/week @ 2024-12-19 8399/week @ 2024-12-26 11979/week @ 2025-01-02 12062/week @ 2025-01-09 11190/week @ 2025-01-16 11363/week @ 2025-01-23 11232/week @ 2025-01-30 14438/week @ 2025-02-06 11970/week @ 2025-02-13 13726/week @ 2025-02-20 13089/week @ 2025-02-27 12066/week @ 2025-03-06 14185/week @ 2025-03-13 12223/week @ 2025-03-20 11739/week @ 2025-03-27

52,101 downloads per month
Used in 14 crates (9 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