| commit | 628255d06aab0b37e9f66d7ad12fc7b67e68c407 | [log] [tgz] |
|---|---|---|
| author | Matthew Maurer <[email protected]> | Tue Mar 07 17:24:05 2023 -0800 |
| committer | Matthew Maurer <[email protected]> | Tue Mar 07 17:24:05 2023 -0800 |
| tree | 8f35d3645086169c660d74ad03160565694afc51 | |
| parent | 06b31b1da2d7a2a62c22c890e17fe6b53c11b4b5 [diff] |
Make itertools available to product and vendor Bug: 270690570 Test: mma in external/rust/crates Change-Id: I3fb9305dacdeb0fafb7aafc90ff9c8bc0405ecb0
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.