| commit | 2bd018b28adbce129288370bc27d7fc683ba5199 | [log] [tgz] |
|---|---|---|
| author | James Farrell <[email protected]> | Wed Aug 07 15:51:56 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Wed Aug 07 15:51:56 2024 +0000 |
| tree | 599f96c7562fd3abc2b3344f62972e59fdfb7a63 | |
| parent | 49862f938fbf98784fc96a149fa98af834013341 [diff] | |
| parent | dab1767057f55c820217f089aa433749350828c2 [diff] |
Update Android.bp by running cargo_embargo am: d0eb1075ea am: dab1767057 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/itertools/+/3208712 Change-Id: If1a706e2df1f089d1365a135d3a2344cc22da572 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.