| commit | 71a7a4b79f387267c4505a1ed43e0e44cfeaf69e | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Sun Aug 11 07:10:46 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Sun Aug 11 07:10:46 2024 +0000 |
| tree | a41d0cfb96f949d5b50d8c9f6554dc5aaa28d454 | |
| parent | 30afdc2de3ccbe1156d6fa266ce1c2d22091a620 [diff] | |
| parent | 2398826d1f3dc3e217872009096c54df24c20953 [diff] |
Snap for 12199977 from 2398826d1f3dc3e217872009096c54df24c20953 to busytown-mac-infra-release Change-Id: I092c746ef9e30973a6c2107afc03a79d271672d5
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.