| commit | eadf29b9bc49f3902750b46e5ba3380171e49f3a | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Fri Mar 10 05:16:41 2023 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Fri Mar 10 05:16:41 2023 +0000 |
| tree | 191129b37d873ce2f0c3603e0ae058b51e1fcb13 | |
| parent | 5ff1cfa76b70abe23357814b32911b2a9d2dc0b4 [diff] | |
| parent | 519c740d636aedc4e023da4917ed87af40a46efd [diff] |
Snap for 9722771 from 519c740d636aedc4e023da4917ed87af40a46efd to udc-d1-release Change-Id: I13c52eef5b83c1f2b50d385e5543d9f773a95738
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.