| commit | 0fb2cb65a5451a248c72f6f6f5b1daaa33f91ef6 | [log] [tgz] |
|---|---|---|
| author | Andrew Walbran <[email protected]> | Wed Oct 18 18:52:44 2023 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Wed Oct 18 18:52:44 2023 +0000 |
| tree | 112d7086a79dc79a19844efeca15a2ce0140305c | |
| parent | 7c93d7aacb5a2810c6919cbcb2ef0f4de48684a4 [diff] | |
| parent | b71722ff58eba763ff65f96a79a02488da9e8602 [diff] |
Migrate to cargo_embargo. am: b71722ff58 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/itertools/+/2796435 Change-Id: Id050b974835e15df0f62b180e4f6e4628a83ac1a 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.