| commit | 46145897e455e1983940f6f6d7cdc5e25e4e6297 | [log] [tgz] |
|---|---|---|
| author | James Farrell <[email protected]> | Tue May 21 15:04:00 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue May 21 15:04:00 2024 +0000 |
| tree | 0a4d18065e3055eb4f44240fc1e2704e45258429 | |
| parent | 9da2e89ca6ff3138dcb86033eaf28c0cb09257b2 [diff] | |
| parent | a1f0cccde3d5de731808dd53300cbb781d8c810c [diff] |
Update Android.bp by running cargo_embargo am: 56209e5a1f am: a1f0cccde3 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/itertools/+/3094309 Change-Id: I5523ce22899315ee3b485a8a353c50812384accf 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.