| commit | 4d9f91ea0b0506501871da5b09677b3068f88e7f | [log] [tgz] |
|---|---|---|
| author | Jeff Vander Stoep <[email protected]> | Tue Jan 31 21:06:08 2023 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue Jan 31 21:06:08 2023 +0000 |
| tree | 6634ac30dc6636eb209a3c7dcc701beb7766cebe | |
| parent | 24d8819288d38db197610f3872f14dea3f3d2305 [diff] | |
| parent | be203ff0d43d8721464e2655bb3ea4a5a6f0bb45 [diff] |
Update TEST_MAPPING am: 06b31b1da2 am: 5871dbacf1 am: be203ff0d4 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/itertools/+/2411596 Change-Id: I929dd9f2158304d06c4607604343680e40d4c994 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.