commit | 106df73fd02c9700fbebe5a08de11e06120b01e3 | [log] [tgz] |
---|---|---|
author | Matthew Maurer <[email protected]> | Thu May 26 11:18:42 2022 -0700 |
committer | Matthew Maurer <[email protected]> | Thu May 26 11:18:42 2022 -0700 |
tree | 2c8ef6f18e504a73099ebefc95785ef3b5faa604 | |
parent | d7c65f3dc39d5876237e3d3e9aa326a0bfbc5826 [diff] |
Update TEST_MAPPING Test: None Bug: 233924440 Change-Id: I8ee913a93eae53e045cf802ba6f79ff71ff25cbf
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.