| commit | 990e4dd9aebf561d7ea6ac3c43d6276e022c5842 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Fri Mar 10 04:19:04 2023 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Fri Mar 10 04:19:04 2023 +0000 |
| tree | 8f35d3645086169c660d74ad03160565694afc51 | |
| parent | 5dc6702447f3d7aeff80ae475c02e8be4ce907dd [diff] | |
| parent | 016dc6488451800719f973f7b79b2c9fb74fd783 [diff] |
Snap for 9719949 from 7c93d7aacb5a2810c6919cbcb2ef0f4de48684a4 to udc-release am: 016dc64884 Original change: https://googleplex-android-review.googlesource.com/c/platform/external/rust/crates/itertools/+/21946782 Change-Id: I95b8b9e823ca8a5050cec35c44bad65acc8888bb 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.