| commit | ffcf82bc3c72288ce6d5c6b4f5b1427d082803d3 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Sun Sep 01 07:11:15 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Sun Sep 01 07:11:15 2024 +0000 |
| tree | 0fa61ce8d46b47648ff5b05f66ad59a61ffb817c | |
| parent | 71a7a4b79f387267c4505a1ed43e0e44cfeaf69e [diff] | |
| parent | 03fe17147099bcfe7e3c8719e6a2844c144e8802 [diff] |
Snap for 12292009 from 03fe17147099bcfe7e3c8719e6a2844c144e8802 to busytown-mac-infra-release Change-Id: I6764fc874aabe47c0257e7dcece54bbd28ca8049
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.
Add the following lines to your “Cargo.toml” file:
[dependencies] os_str_bytes = "6.4"
See the documentation for available functionality and examples.
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"
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.