| commit | f0e1978863ba9b60fd785e1f7d17dbeb08410527 | [log] [tgz] |
|---|---|---|
| author | James Farrell <[email protected]> | Thu May 09 20:06:22 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Thu May 09 20:06:22 2024 +0000 |
| tree | 4ebdd504c5de164db5c82bd45a85d27c3d6a677b | |
| parent | 8139fb107a8cb8c8f39970995c914ee922a51dfa [diff] | |
| parent | 25cb0e25e55ed64a7f6101104f668501e3f79d5f [diff] |
Update Android.bp by running cargo_embargo am: 25cb0e25e5 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/itertools/+/3080548 Change-Id: Ie75dc2cb3e9c04031c84af19a81050b005ca3600 Signed-off-by: Automerger Merge Worker <[email protected]>
Extra iterator adaptors, functions and macros.
Please read the API documentation here.
How to use with Cargo:
[dependencies] itertools = "0.10.5"
How to use in your crate:
use itertools::Itertools;
For new features, please first consider filing a PR to rust-lang/rust, adding your new feature to the Iterator trait of the standard library, if you believe it is reasonable. If it isn‘t accepted there, proposing it for inclusion in itertools is a good idea. The reason for doing is this is so that we avoid future breakage as with .flatten(). However, if your feature involves heap allocation, such as storing elements in a Vec<T>, then it can’t be accepted into libcore, and you should propose it for itertools directly instead.
Dual-licensed to be compatible with the Rust project.
Licensed under the Apache License, Version 2.0 https://www.apache.org/licenses/LICENSE-2.0 or the MIT license https://opensource.org/licenses/MIT, at your option. This file may not be copied, modified, or distributed except according to those terms.