| commit | badd28067fcec4ba5bf692aaf2fc39c9cec10a9d | [log] [tgz] |
|---|---|---|
| author | Jeff Vander Stoep <[email protected]> | Tue Dec 13 17:41:26 2022 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue Dec 13 17:41:26 2022 +0000 |
| tree | e74967a2ccaad34b918be498fe7f0d7b64c90527 | |
| parent | 5d2fd3007cb69905e0eb3397527471c25859c651 [diff] | |
| parent | 01180d8d339214181adefba44757fde3439e155e [diff] |
Update os_str_bytes to 6.4.1 am: f983a87abb am: 01180d8d33 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/os_str_bytes/+/2345753 Change-Id: I991aae5697ecf559079146e012f0bf4d489b7c72 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.