commit | 36c9eadbeb7d5a205cd41268b5cd95429dec32a8 | [log] [tgz] |
---|---|---|
author | Jeff Vander Stoep <jeffv@google.com> | Mon Dec 12 13:40:25 2022 +0100 |
committer | Jeff Vander Stoep <jeffv@google.com> | Mon Dec 12 13:41:05 2022 +0100 |
tree | 8e0a28233ae31fcd4f59965958c208c3cbb61ee4 | |
parent | fa1af4a035e6372f2bbbe1e1bec48df176a47a42 [diff] |
Upgrade itertools to 0.10.5 This project was upgraded with external_updater. Usage: tools/external_updater/updater.sh update rust/crates/itertools For more info, check https://cs.android.com/android/platform/superproject/+/master:tools/external_updater/README.md Test: TreeHugger Change-Id: I04ecd1d5827d6d1822997f324e6bac8e8bd8ea83
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.