| commit | 9cc71eba7df9f875aaf587d3b700940e931cc974 | [log] [tgz] |
|---|---|---|
| author | Jeff Vander Stoep <[email protected]> | Tue Jan 31 19:36:01 2023 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue Jan 31 19:36:01 2023 +0000 |
| tree | 5853e3ba5f50b64e4baa153d15fd48b8cd7fbe2c | |
| parent | 77cf3c3b524532fc3048cd1ef0303b023d830a87 [diff] | |
| parent | 58987e139a94ed46cfe2be9c642f0ca70f25cef5 [diff] |
Update TEST_MAPPING am: 58987e139a Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/os_str_bytes/+/2411801 Change-Id: I146a14fb4be7a8b8e7def9e62dc705cf1829f4c5 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.