commit | 275b267e11607f6277e4e01aca30edc9aa6a0069 | [log] [tgz] |
---|---|---|
author | Matthew Maurer <mmaurer@google.com> | Tue May 31 15:54:36 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue May 31 15:54:36 2022 +0000 |
tree | 2c8ef6f18e504a73099ebefc95785ef3b5faa604 | |
parent | 3046cfa45bb4c52c96e1ec72a1ebd8a404e4bf85 [diff] | |
parent | 106df73fd02c9700fbebe5a08de11e06120b01e3 [diff] |
Update TEST_MAPPING am: 106df73fd0 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/itertools/+/2108493 Change-Id: Ieec2334ffaaa741f81575723f09951aa42a7ac8e 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.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.