Bug: 238905913

Clone this repo:
  1. 314e342 Update Android.bp by running cargo_embargo am: 59c6735188 by James Farrell · 4 weeks ago main master
  2. 59c6735 Update Android.bp by running cargo_embargo by James Farrell · 4 weeks ago
  3. d24c687 Update Android.bp by running cargo_embargo am: bc48656205 by James Farrell · 5 weeks ago
  4. bc48656 Update Android.bp by running cargo_embargo by James Farrell · 6 weeks ago
  5. 652424e Update min_sdk_version to 29 am: 1c74488f02 by Ted Bauer · 3 months ago

OsStr Bytes

This crate allows interacting with the data stored by OsStr and OsString, without resorting to panics or corruption for invalid UTF-8. Thus, methods can be used that are already defined on [u8] and Vec<u8>.

Typically, the only way to losslessly construct OsStr or OsString from a byte sequence is to use OsStr::new(str::from_utf8(bytes)?), which requires the bytes to be valid in UTF-8. However, since this crate makes conversions directly between the platform encoding and raw bytes, even some strings invalid in UTF-8 can be converted.

GitHub Build Status

Usage

Add the following lines to your “Cargo.toml” file:

[dependencies]
os_str_bytes = "6.4"

See the documentation for available functionality and examples.

Rust version support

The minimum supported Rust toolchain version depends on the platform:

Minor version updates may increase these version requirements. However, the previous two Rust releases will always be supported. If the minimum Rust version must not be increased, use a tilde requirement to prevent updating this crate's minor version:

[dependencies]
os_str_bytes = "~6.4"

License

Licensing terms are specified in COPYRIGHT.

Unless you explicitly state otherwise, any contribution submitted for inclusion in this crate, as defined in LICENSE-APACHE, shall be licensed according to COPYRIGHT, without any additional terms or conditions.