| commit | ddd48619f716c154a999e793554f8be49afe0673 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Tue May 21 23:14:13 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Tue May 21 23:14:13 2024 +0000 |
| tree | 51ad6a9baac5fa633b6d2511c723bee1d0f72a22 | |
| parent | d7e8e81259df10a0162f25ec3b0552827e7c07c2 [diff] | |
| parent | 9eecb3f598ddf9db22e7a535118214c8ba55eacb [diff] |
Snap for 11869550 from 9eecb3f598ddf9db22e7a535118214c8ba55eacb to 24Q3-release Change-Id: I538375a904b89e7ec5e9aad906e664dbb98f7d71
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.