| commit | 76d5a0ce61f713b2113a204532e2a087561798fe | [log] [tgz] |
|---|---|---|
| author | James Farrell <[email protected]> | Thu May 09 20:27:42 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Thu May 09 20:27:42 2024 +0000 |
| tree | 5095a5e324d7482b5dfe74514706c2d920d8e0c9 | |
| parent | 3682f9626bc696f5c470974d6455cf8ec2ebf402 [diff] | |
| parent | d24c687ee5e4f50c6e237406bb7ded799dbf421d [diff] |
Update Android.bp by running cargo_embargo am: bc48656205 am: d24c687ee5 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/os_str_bytes/+/3080490 Change-Id: Ibb562428677d6d1f9998d4eae274c81cfa089c11 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.