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

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

#1570 in Text processing

Download history 9210/week @ 2024-09-25 10480/week @ 2024-10-02 8906/week @ 2024-10-09 10582/week @ 2024-10-16 11837/week @ 2024-10-23 10876/week @ 2024-10-30 10257/week @ 2024-11-06 12934/week @ 2024-11-13 13228/week @ 2024-11-20 13416/week @ 2024-11-27 10994/week @ 2024-12-04 14056/week @ 2024-12-11 13132/week @ 2024-12-18 8107/week @ 2024-12-25 11556/week @ 2025-01-01 10020/week @ 2025-01-08

44,988 downloads per month
Used in 13 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