| commit | 3682f9626bc696f5c470974d6455cf8ec2ebf402 | [log] [tgz] |
|---|---|---|
| author | Ted Bauer <[email protected]> | Fri Mar 29 00:18:20 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Fri Mar 29 00:18:20 2024 +0000 |
| tree | c7a314515145e78b5f02dab3a18613532d792a4a | |
| parent | e90a703f44eea2f79793ed299550d317bf04af40 [diff] | |
| parent | 652424e6acf9eaf0809f82274a57bf9a3faf74e3 [diff] |
Update min_sdk_version to 29 am: 1c74488f02 am: 652424e6ac Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/os_str_bytes/+/3017901 Change-Id: If10cce74dc32faa389c328bce977af8e7271e662 Signed-off-by: Automerger Merge Worker <[email protected]>
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.