| commit | 9812a387147ac7bf57a7f04108fbab3afeb2137a | [log] [tgz] |
|---|---|---|
| author | Treehugger Robot <[email protected]> | Thu Jun 16 00:20:39 2022 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Thu Jun 16 00:20:39 2022 +0000 |
| tree | d7d800f84b0d4ccd703059529235b632ba6bc92c | |
| parent | 329a1451d2aea082f62637400b4d7f2e2aeb657c [diff] | |
| parent | fa6a05c7d55d0eef0248c9028062ec1a569f5cff [diff] |
Merge "Update TEST_MAPPING" am: 60cd39ee56 am: 4ba3f52e9a am: fa1af4a035 am: f3b2dd34f5 am: fa6a05c7d5 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/itertools/+/2125942 Change-Id: I7b548b6bafbadaad850804e3dd5db119c5fb5df1 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.2"
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.