| commit | 8a7b4c8bd768f634efd95c32336e2cd35529b6e5 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Wed Feb 07 00:14:30 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Wed Feb 07 00:14:30 2024 +0000 |
| tree | 4b29caddb5fb6ef3d61025c0e200e7447449c8d0 | |
| parent | 6d3c278eb28d1a921a88e78ccd2cb508511023b2 [diff] | |
| parent | d45fee5728b5f0ebd55396b8921ec57d60a56da8 [diff] |
Snap for 11413429 from d45fee5728b5f0ebd55396b8921ec57d60a56da8 to 24D1-release Change-Id: I9c48ccf5b8bf83c2670a6bb30de658ef52295965
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.