| Crates.io | byte_string |
| lib.rs | byte_string |
| version | 1.0.0 |
| created_at | 2016-09-26 00:50:24.486801+00 |
| updated_at | 2016-09-26 00:50:24.486801+00 |
| description | Wrapper types for outputting byte strings (b"Hello") using the Debug ({:?}) format. |
| homepage | |
| repository | https://github.com/FraGag/byte_string |
| max_upload_size | |
| id | 6629 |
| size | 27,695 |
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.
byte_string is licensed under the terms of both the MIT license and the Apache License, version 2.0.