| commit | e90a703f44eea2f79793ed299550d317bf04af40 | [log] [tgz] |
|---|---|---|
| author | Andrew Walbran <[email protected]> | Tue Nov 14 20:46:12 2023 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue Nov 14 20:46:12 2023 +0000 |
| tree | 1fa441f65c917e0185ed344b31c75275efa586c2 | |
| parent | 4b5cb5571fa4b88af4afbdc9679b951d76f0b18c [diff] | |
| parent | a7699f875940ba00e2495f9f2e8a71cd9c2f53de [diff] |
Migrate to cargo_embargo. am: 05b35cb48a am: e433ed5cd7 am: a7699f8759 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/os_str_bytes/+/2828069 Change-Id: I7ddbcb0286e33816c7132dfa7d95a9e47b358e6b 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.