commit | 5e83ffed11f39804ac50b6d022406ac4f50adf01 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <[email protected]> | Tue Oct 01 23:13:39 2024 +0000 |
committer | Android Build Coastguard Worker <[email protected]> | Tue Oct 01 23:13:39 2024 +0000 |
tree | 44734bfc6ecb9e2139e00591470efe53ad37737d | |
parent | f3a8780a8ca11bd55e736be49e1bde72190c6d86 [diff] | |
parent | 9ebbfde82cb6ab9b64650a16a68986f0e2c5c268 [diff] |
Snap for 12440112 from 9ebbfde82cb6ab9b64650a16a68986f0e2c5c268 to sdk-release Change-Id: I9d0785069a1399cb509a0872e7d04705c42d5587
Same idea as (but implementation not directly based on) the Python shlex module. However, this implementation does not support any of the Python module's customization because it makes parsing slower and is fairly useless. You only get the default settings of shlex.split, which mimic the POSIX shell: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html
This implementation also deviates from the Python version in not treating \r specially, which I believe is more compliant.
This crate can be used on either normal Rust strings, or on byte strings with the bytes
module. The algorithms used are oblivious to UTF-8 high bytes, so internally they all work on bytes directly as a micro-optimization.
Disabling the std
feature (which is enabled by default) will allow the crate to work in no_std
environments, where the alloc
crate, and a global allocator, are available.
The source code in this repository is Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.