commit | 49f788bc75f2165c276fb98e9aacb38e3d3d4de0 | [log] [tgz] |
---|---|---|
author | David LeGare <legare@google.com> | Fri Mar 04 01:33:29 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Mar 04 01:33:29 2022 +0000 |
tree | 0ca62eb5d0beeab0cb7ee3c0db8111e81788c2cd | |
parent | fae9763752c225bbbcfa423a1ea6f5f7f2a74d71 [diff] | |
parent | b72e905c595b81ee7ac7654f4fb3e0db460be21a [diff] |
Update itertools to 0.10.3 am: b72e905c59 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/itertools/+/2005035 Change-Id: Iacad5e48ca1d13b543a2a4add14dd6c4c8d98cad
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.