| commit | b71722ff58eba763ff65f96a79a02488da9e8602 | [log] [tgz] |
|---|---|---|
| author | Andrew Walbran <qwandor@google.com> | Wed Oct 18 17:54:43 2023 +0100 |
| committer | Andrew Walbran <qwandor@google.com> | Wed Oct 18 17:54:43 2023 +0100 |
| tree | 112d7086a79dc79a19844efeca15a2ce0140305c | |
| parent | 7c93d7aacb5a2810c6919cbcb2ef0f4de48684a4 [diff] |
Migrate to cargo_embargo. Bug: 293289578 Test: Ran cargo_embargo, compared Android.bp Change-Id: Ic575aeaaf356a14b42f0d2b1f182b3c97ad12b9d
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.