| commit | 35896f4dea3b52fd017bf84b3cd86c9054091080 | [log] [tgz] |
|---|---|---|
| author | James Farrell <jamesfarrell@google.com> | Wed Aug 28 15:34:20 2024 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Aug 28 15:34:20 2024 +0000 |
| tree | 43f28f10d8ed3b8be61b44f2d57f00a162feaeec | |
| parent | 2bd018b28adbce129288370bc27d7fc683ba5199 [diff] | |
| parent | a6c6d18e2bf87ab642356e12dcae5014ffc0b70a [diff] |
Migrate 25 crates to monorepo. am: 8879908044 am: a6c6d18e2b Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/itertools/+/3243829 Change-Id: I57a570a92171239de9f6987f44db62d56ad3a62a Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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.