| commit | 9eecb3f598ddf9db22e7a535118214c8ba55eacb | [log] [tgz] |
|---|---|---|
| author | James Farrell <[email protected]> | Tue May 21 15:04:08 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue May 21 15:04:08 2024 +0000 |
| tree | 51ad6a9baac5fa633b6d2511c723bee1d0f72a22 | |
| parent | 76d5a0ce61f713b2113a204532e2a087561798fe [diff] | |
| parent | 314e34261b681f61e9434909c0bec251aa745ff0 [diff] |
Update Android.bp by running cargo_embargo am: 59c6735188 am: 314e34261b Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/os_str_bytes/+/3095490 Change-Id: I01f4e39a07dc9d8aa12e9785069155c387183fe6 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.