| commit | 2f88f491b364a6a3c3b495965d6562384bb7b30c | [log] [tgz] |
|---|---|---|
| author | Sam Saccone <[email protected]> | Tue Jul 18 19:08:33 2023 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue Jul 18 19:08:33 2023 +0000 |
| tree | 182e2d537aaf9c9244df0e5bf09f62031f916dd2 | |
| parent | 2244b55ebea99435b5c2aba5975be19d64f36142 [diff] | |
| parent | 6372ea42f7639212701d45323149c465b9f05901 [diff] |
Move OWNER reference master=>main. am: 6372ea42f7 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/os_str_bytes/+/2661147 Change-Id: I42e1645397979def87e37b33df2785f24ebddb03 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.