| commit | da75ba104e8939e6ab905c2d3b09ef8d43ae9a22 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Sun Mar 06 10:04:19 2022 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Sun Mar 06 10:04:19 2022 +0000 |
| tree | d7d800f84b0d4ccd703059529235b632ba6bc92c | |
| parent | 0077610a4232dd2bbe1ed644dc717a3e2d815e7a [diff] | |
| parent | 0c1f919fd338a10642e2a13a31635febc81f023f [diff] |
Snap for 8261789 from 0c1f919fd338a10642e2a13a31635febc81f023f to main-cg-testing-release Change-Id: I088b9497608b174a20cbca8dbdb20749c727a99c
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.