| commit | 61f5aa697526576b3d872c5abafe366ca895c336 | [log] [tgz] |
|---|---|---|
| author | Matthew Maurer <[email protected]> | Thu Mar 09 15:13:11 2023 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Thu Mar 09 15:13:11 2023 +0000 |
| tree | 8f35d3645086169c660d74ad03160565694afc51 | |
| parent | 5871dbacf11e0590f9e7b1289995d43b4fe58b0b [diff] | |
| parent | 628255d06aab0b37e9f66d7ad12fc7b67e68c407 [diff] |
Make itertools available to product and vendor am: 628255d06a Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/itertools/+/2476416 Change-Id: I9b7482ee1a5ed047bcdc1bfe217ea0b3be8d6469 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.