commit | 5a03ba3cb246bc0cc1d8514e1323a0426304ad1d | [log] [tgz] |
---|---|---|
author | Treehugger Robot <treehugger-gerrit@google.com> | Mon Dec 12 21:16:40 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Dec 12 21:16:40 2022 +0000 |
tree | 8e0a28233ae31fcd4f59965958c208c3cbb61ee4 | |
parent | fa6a05c7d55d0eef0248c9028062ec1a569f5cff [diff] | |
parent | d83b1d14f2239326229629bc960e1cb7c9102b67 [diff] |
Merge "Upgrade itertools to 0.10.5" am: 79f88bdd7d am: d83b1d14f2 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/itertools/+/2344982 Change-Id: Ifaffc2523449cda2f39d3e62ba820238c55cb875 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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.