| commit | f3c720cef214709cab13fa6896b7869919996960 | [log] [tgz] |
|---|---|---|
| author | Andrew Walbran <[email protected]> | Wed Oct 18 19:48:47 2023 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Wed Oct 18 19:48:47 2023 +0000 |
| tree | 112d7086a79dc79a19844efeca15a2ce0140305c | |
| parent | ce6a773e5db80859c3ba9122a92e844295717529 [diff] | |
| parent | 354adf354dfdc288f7d09f04c1ef10eec8b9a6fd [diff] |
Migrate to cargo_embargo. am: b71722ff58 am: 3205c21f66 am: 354adf354d Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/itertools/+/2796435 Change-Id: I69309d1be02a40297fa5cf908aa3828be5d342f2 Signed-off-by: Automerger Merge Worker <[email protected]>
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.