commit | d350ae8f4117dbaed9af7c3b0b497e62a90c3306 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Mar 18 10:08:54 2022 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Mar 18 10:08:54 2022 +0000 |
tree | d7d800f84b0d4ccd703059529235b632ba6bc92c | |
parent | 0ddf37c48b8d3af9cde1e8368cc16b37a8e3271b [diff] | |
parent | 436b88261e035f982767639db0cffee538ea8b61 [diff] |
Snap for 8319971 from 436b88261e035f982767639db0cffee538ea8b61 to t-keystone-qcom-release Change-Id: Iac487e8569ae8cec36a005316fa8cbd12b468992
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.